[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
This was fixed in nfs-utils. Closing upstart tasks as they are no longer necessary. ** Changed in: upstart (Ubuntu) Status: Confirmed = Won't Fix ** Changed in: upstart (Ubuntu) Status: Won't Fix = Invalid ** Changed in: upstart (Ubuntu Utopic) Status: Confirmed = Invalid ** Changed in: upstart (Ubuntu Vivid) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Invalid Status in nfs-utils source package in Utopic: Fix Released Status in upstart source package in Utopic: Invalid Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Invalid Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu1.1 --- nfs-utils (1:1.2.8-9ubuntu1.1) utopic; urgency=medium * debian/nfs-common.statd.upstart: wait for rpcbind job instead of relying on portmap compatibility event. (LP: #1391296) -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 18 Nov 2014 19:07:15 -0500 ** Changed in: nfs-utils (Ubuntu Utopic) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Released Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
FWIW, the package in utopic-proposed fixes the issue for me. I'm not marking as verification-done, as I would really like for someone else who is affected by this bug to test it also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
The fix in proposed fixed this problem on two separate boxes for me. Would be great to see this in the main repository. thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
Hello Tommy, or anyone else affected, Accepted nfs-utils into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nfs- utils/1:1.2.8-9ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nfs-utils (Ubuntu Utopic) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Fix Committed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Branch linked: lp:ubuntu/utopic-proposed/nfs-utils -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Fix Committed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Description changed: + [SRU Request] + + Due to a change in Upstart behaviour, the statd daemon no longer starts + automatically at boot, resulting in nfs mounts not being mounted at + boot. + + This has been corrected by modifying the statd upstart job to wait for + the rpcbind job to start, instead of waiting for the compatibility + portmap event. + + [Test Case] + 1- set up an NFS mount in /etc/fstab + 2- Reboot, notice the directory didn't get mounted + 3- Install update + 4- Reboot, notice the directory is mounted + + [Regression Potential] + The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. + + + Original description: + After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 ** Changed in: nfs-utils (Ubuntu Utopic) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: In Progress Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Changed in: nfs-utils (Ubuntu Utopic) Importance: Undecided = High ** Changed in: nfs-utils (Ubuntu Vivid) Importance: Undecided = High ** Changed in: upstart (Ubuntu Utopic) Importance: Undecided = High ** Changed in: upstart (Ubuntu Vivid) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: In Progress Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
*** This bug is a duplicate of bug 1384502 *** https://bugs.launchpad.net/bugs/1384502 ** This bug has been marked a duplicate of bug 1384502 fstab entry for nfs /home fails to mount on boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “mountall” package in Ubuntu: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
Upstart shouldn't require an INSTANCE variable for that to work, and nfs-utils shouldn't be waiting on the portmap job, as that is for legacy compatibility only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
Ok, I've investigated this, and it turns out: statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be run statd.conf starts on (virtual-filesystems and started portmap ON_BOOT=y) rpcbind.conf is what emits the started portmap event: # For compatibility with older upstart jobs in Ubuntu post-start exec initctl emit --no-wait started JOB=portmap ON_BOOT=$ON_BOOT pre-stop exec initctl emit --no-wait stopping JOB=portmap But, to actually work with upstart in 14.10, the INSTANCE variable has to be added, like so: # For compatibility with older upstart jobs in Ubuntu post-start exec initctl emit --no-wait started JOB=portmap INSTANCE='' ON_BOOT=$ON_BOOT pre-stop exec initctl emit --no-wait stopping JOB=portmap INSTANCE='' ** This bug is no longer a duplicate of bug 1384502 fstab entry for nfs /home fails to mount on boot ** Package changed: mountall (Ubuntu) = upstart (Ubuntu) ** Also affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: nfs-utils (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Also affects: nfs-utils (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: upstart (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: nfs-utils (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: upstart (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: nfs-utils (Ubuntu Utopic) Status: New = Confirmed ** Changed in: upstart (Ubuntu Utopic) Status: New = Confirmed ** Changed in: nfs-utils (Ubuntu Utopic) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: nfs-utils (Ubuntu Vivid) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Confirmed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Confirmed Status in “upstart” source package in Vivid: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** Branch linked: lp:ubuntu/vivid-proposed/nfs-utils -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Confirmed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Confirmed Status in “upstart” source package in Vivid: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu2 --- nfs-utils (1:1.2.8-9ubuntu2) vivid; urgency=medium * debian/nfs-common.statd.upstart: wait for rpcbind job instead of relying on portmap compatibility event. (LP: #1391296) -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 18 Nov 2014 19:07:15 -0500 ** Changed in: nfs-utils (Ubuntu Vivid) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Confirmed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
Any chance of seeing a fix for utopic for this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “nfs-utils” package in Ubuntu: Fix Released Status in “upstart” package in Ubuntu: Confirmed Status in “nfs-utils” source package in Utopic: Confirmed Status in “upstart” source package in Utopic: Confirmed Status in “nfs-utils” source package in Vivid: Fix Released Status in “upstart” source package in Vivid: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mountall (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in “mountall” package in Ubuntu: Confirmed Bug description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1391296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp