Activity log for bug #470776

Date Who What changed Old value New value Message
2009-11-02 13:48:16 hmpl bug added bug
2009-11-02 13:48:16 hmpl attachment added mountall.log http://launchpadlibrarian.net/34954903/mountall.log
2009-11-09 15:26:56 Scott James Remnant (Canonical) summary karmic: nfs shares not mounted on boot with ro-root retry remote devices when parent is ready after SIGURS1
2009-11-09 15:27:02 Scott James Remnant (Canonical) summary retry remote devices when parent is ready after SIGURS1 retry remote devices when parent is ready after SIGUSR1
2009-11-09 15:27:04 Scott James Remnant (Canonical) mountall (Ubuntu): status New Triaged
2009-11-09 15:27:08 Scott James Remnant (Canonical) mountall (Ubuntu): importance Undecided Medium
2009-12-21 15:49:08 Scott James Remnant (Canonical) mountall (Ubuntu): status Triaged Fix Committed
2009-12-21 15:49:15 Scott James Remnant (Canonical) mountall (Ubuntu): milestone lucid-alpha-2
2009-12-21 15:49:19 Scott James Remnant (Canonical) mountall (Ubuntu): assignee Scott James Remnant (scott)
2009-12-21 23:10:30 Launchpad Janitor mountall (Ubuntu): status Fix Committed Fix Released
2010-01-08 06:07:44 Johan Walles nominated for series Ubuntu Karmic
2010-01-09 12:34:15 Dan attachment added Mark all remote filesystems "ready" after SIGUSR1 is received http://launchpadlibrarian.net/37644300/mark-remote-ready.debdiff
2010-01-12 09:59:14 Alvin bug task added ubuntu-release-notes
2010-01-26 16:49:35 Dan tags verification-needed
2010-04-01 20:30:39 John Franklin description Binary package hint: mountall Hi, I have a similar problem like in https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/461133 . My NFS-Shares are not mounted at boot time. But I don't think both problems have the same cause. I think my problem is more related to https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/446678 , but I'm not sure. Release: Ubuntu 9.10 This is what happens: - Grub (still old Grub) line is: /vmlinuz-2.6.31-14-generic root=/dev/mapper/system-lvgggroot ro quiet splash - root is mounted readonly due to Grubline - After Network is up, mountall receives SIGUSR1 (as expected) - At this time root is not yet remounted RW and NFS-Shares cannot be mounted: usr1_handler: Received SIGUSR1 (network device up) try_mount: /Bignfs waiting for / try_mount: /Backnfs waiting for / usr1_handler: Received SIGUSR1 (network device up) try_mount: /Bignfs waiting for / try_mount: /Backnfs waiting for / - After root is remounted, NFS-Shares will not be mounted as they are waiting for SIGUSR1 try_mount: /Bignfs waiting for device gigakobold.daheim:udatanoback try_mount: /Backnfs waiting for device gigakobold.daheim:udataback - mountall will continue running - Sending SIGUSR1 manually will get everything mounted and mountall exits normally So the problem is: Mountall doesn't remember having SIGUSR1 (i.e. network up) already received. So if there is a problem with NFS-mounts while signal from network up is received and the NFS-filesystems cannot be mounted at this time, later retries will not work, too. Regards Markus Binary package hint: mountall Hi, I have a similar problem like in https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/461133 . My NFS-Shares are not mounted at boot time. But I don't think both problems have the same cause. I think my problem is more related to https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/446678 , but I'm not sure. Release: Ubuntu 9.10 This is what happens: - Grub (still old Grub) line is: /vmlinuz-2.6.31-14-generic root=/dev/mapper/system-lvgggroot ro quiet splash - root is mounted readonly due to Grubline - After Network is up, mountall receives SIGUSR1 (as expected) - At this time root is not yet remounted RW and NFS-Shares cannot be mounted:   usr1_handler: Received SIGUSR1 (network device up)   try_mount: /Bignfs waiting for /   try_mount: /Backnfs waiting for /   usr1_handler: Received SIGUSR1 (network device up)   try_mount: /Bignfs waiting for /   try_mount: /Backnfs waiting for / - After root is remounted, NFS-Shares will not be mounted as they are waiting for SIGUSR1   try_mount: /Bignfs waiting for device gigakobold.daheim:udatanoback   try_mount: /Backnfs waiting for device gigakobold.daheim:udataback - mountall will continue running - Sending SIGUSR1 manually will get everything mounted and mountall exits normally So the problem is: Mountall doesn't remember having SIGUSR1 (i.e. network up) already received. So if there is a problem with NFS-mounts while signal from network up is received and the NFS-filesystems cannot be mounted at this time, later retries will not work, too. Regards Markus
2010-04-29 05:48:20 Steve Langasek ubuntu-release-notes: status New Won't Fix