[Touch-packages] [Bug 1313513] Re: mountall does not honour _netdev
In ubuntu 14.05.5 I am running into the same issue. I have a iscsi device added in fstab with _netdev switch but doesnt' seem to work. system just hangs at boot, i have to go into recovery mode to comment out the filesystem to get the system to boot. Interested in what others have done as a work around ? appreciate inputs. Thanks, Vj -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
I have a similar problem when trying to mount a cephfs volume on ubuntu 14.04. It just freezes and I can't do anything about it. I'm unable to figure out why it fails. I am running OpenvSwitch, what I see in boot log is something like this: * Starting configure network device * Starting configure network device security * Starting configure network device security * Starting Mount network filesystems * Starting configure network device * Starting configure network device security * Stopping Mount network filesystems * Starting Mount network filesystems * Starting configure network device * Starting Open vSwitch switch * Stopping Mount network filesystems _ (it's stuck here forever) And my fstab looks like this 10.3.60.25,10.3.60.23,10.3.60.21:/opennebula /var/lib/one ceph _netdev,mount_timeout=10,name=opennebula_cephfs,secretfile=/etc/ceph/ceph.client.opennebula_cephfs.secret 0 0 However worth mentioning that one of the IP's in the list is this machine itself.. In this case second in the list, 10.3.60.23. -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
I seem to be running into this bug on a new build of 14.04.4 when using an LVM on a multipathed ISCSI drive which I am trying to mount at /var/lib/mysql. I'm no upstart guru, so if there is anything I can post to help verify if it is this bug that is causing an issue please let me know. If I just add the 'nobootwait' option to fstab will mysql still wait till the iscsi drive is mounted correctly? Thanks, Steve -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
OK. Couldn't find another bug about this with systemd, so created #1536294. -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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
Re: [Touch-packages] [Bug 1313513] Re: mountall does not honour _netdev
On Wed, Jan 20, 2016 at 12:52:34PM -, Jonathan Kamens wrote: > P.S. for me, it's 15.10 that's not working. You're on the wrong bug. Mountall is an upstart-specific package, which is not used for mounting in systemd systems (15.04 and later). -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
By the way, in my case it appears to be because mount can't resolve the host name of the CIFS file server. I think this is because systemd is trying to mount the filesystems before the nameserver is finished launching, so perhaps if bind9.service is enabled on the host, systemd needs to wait for it to start before mounting network filesystems? -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
I'm really not sure what to make of all this. My fstab has several cifs filesystems in it, and none of them mount at boot regardless of whether _netdev is specified. I don't know whether that's because of this bug -- it's not even clear to me _exactly_ what this bug is about -- or some other bug that is or is not in the database already. I don't know what I can do to help move the process forward of getting this issue -- which apparently affects other people besides me -- fixed. I'm surprised that this bug is almost two years old and nobody seems to care about the fact that network filesystems in /etc/fstab don't work on Ubuntu. P.S. for me, it's 15.10 that's not working. -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
Actually, I was wrong, it's not because of DNS problems, it's because systemd is trying to mount the filesystems before the network is up. I changed the host names in /etc/fstab to IP addresses, and it still doesn't work: Jan 20 08:17:31 jik5 mount[979]: mount error(101): Network is unreachable So there is something here that is definitely not working properly. -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
Fixed for me by putting this in /etc/systemd/system/remote-fs- pre.target.d/override.conf: [Unit] Requires=NetworkManager-wait-online.service After=NetworkManager-wait-online.service -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
IMO it is not enough to say obsolete documentation, someone should remove it. Some of us have been using *nix for years (or decades), and some of these facilities have been developed and stabilized years ago. We rely on things that used to work to keep working. At the very least, one should revise old documentation to clarify that some older method has been deprecated (as in java documentation), and the new method should be referenced, together with conversion methods and/or tools. We want to build on previous work. We don't want all of our sand castles to fall down. In my case, I also find that _netdev does not work on a recent installation of Ubuntu 14.04.2 LTS (upgraded to .3) on Lenovo D20 (dual Xeon), but mysteriously it DOES work on a 1 y.o. installation (upgraded to 14.04.3 LTS) on HP 500-189 (AMD A10). That suggests to me that there must be some interaction(s) between packages? My old installation has everything (including the kitchen sink), but my new installation is rather spare (tho not exactly minimum). What is annoying is I want/need to NFS mount my /home directories on my new install as well. I will try autofs (waits longer, delaying during remainder of boot, until I try to login) instead of hard NFS mount during boot sequence. Still, it is annoying when things that used to work suddenly stop working. -- 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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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 1313513] Re: mountall does not honour _netdev
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/1313513 Title: mountall does not honour _netdev Status in mountall package in Ubuntu: Confirmed Bug description: Hi, This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried configuring a Ceph Rados Block Device (rbd) to be mounted during boot on /var/lib/one, containing my OpenNebula configuration and database. The idea being that should the machine go belly up, I'll have an up- to-date snapshot of the OpenNebula data on Ceph to mount on the new frontend machine. /etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry: /dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1 then rebooted. According to mount(8), _netdev is supposed to tell mountall to skip mounting this device until the network is up. As seen from the attached snapshot, it doesn't bother to wait, and blindly tries to mount the RBD before connecting to Ceph: this will never work. mountall seems to rely on *knowing* a list of network file systems: this means when someone comes up with a new network file system, or uses a conventional disk file system with a remote block device, mountall's heuristic falls flat on its face as has been demonstrated here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd and drbd devices. Due to bug 1313497, the keyboard is non-functional. Recovery is useless as the keyboard is broken there too, and now the machine is waiting for a keypress it will never see due to that bug. A headless system would similarly have this problem. Two suggestions I would have: 1. mountall should honour _netdev to decide whether to mount a device or not: this gives the user the means to manually tell mountall that the device needs network access to operate even if the filesystem looks to be local. I'd wager that if the user specified _netdev, they probably meant it and likely know better than mountall. 2. mountall should time out after a predefined period and NEVER wait indefinitely: even if the disk is local. If a disk goes missing, then it is better the machine tries to boot in its degraded state so it can be remotely managed and raise an alarm, than to wait for someone to notice the machine being down. Unfortunately since the machine is now effectively bricked, I can only grep proxy server logs to see what packages got installed. mountall_2.53_amd64.deb seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1313513/+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
