[Bug 929482] Re: unmounted-remote-filesystems event deadlocks nfs-root

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sysvinit (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/929482

Title:
  unmounted-remote-filesystems event deadlocks nfs-root

Status in “sysvinit” package in Ubuntu:
  Confirmed

Bug description:
  From the changelog:

  sysvinit (2.87dsf-4ubuntu17.5) lucid-proposed; urgency=low

    * debian/initscripts/etc/init.d/umountnfs.sh: emit a new event,
      unmounted-remote-filesystems, to allow stopping portmap
      and others. (LP: #711425)
   -- Clint Byrum <clint at ubuntu.com>   Fri, 20 Jan 2012 01:15:42 -0800

  Updating from this package makes the system hang on shutdown:

   * All processes ended within 1 seconds....                              [ OK ] 
  init: Connection from private client
  init: Handling unmounted-remote-filesystems event
  init: portmap goal changed from start to stop
  init: portmap state changed from running to pre-stop
  init: portmap pre-stop process (2672)
  init: portmap pre-stop process (2672) exited normally
  init: portmap state changed from pre-stop to stopping
  init: Handling stopping event
  init: statd goal changed from start to stop
  init: statd state changed from running to pre-stop
  init: statd state changed from pre-stop to stopping
  init: Handling stopping event
  init: statd state changed from stopping to killed
  init: Sending TERM signal to statd main process (856)

  The system is using nfsroot so / is mounted as NFS and remains
  mounted. In that case I think it is wrong to emit the umounted-remote-
  filesystem event.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/929482/+subscriptions