[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-05 Thread gregrwm
/ (sdb2) was mounted at 10 seconds, nothing other than fsck proceeded between 27 and 301 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1115600 Title: nobootwait no longer averts waiting

[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-05 Thread gregrwm
the attached syslog.snip shows that 299 seconds elapsed before (the completion of fscks allowed) mounting of sde1 and subsequent launching of bluetooth, kdm, (and ssh and getty) ** Attachment added: fstab

[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-05 Thread gregrwm
** Attachment added: syslog.snip https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1115600/+attachment/3515828/+files/syslog.snip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1115600

[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-05 Thread gregrwm
perhaps nobootwait needs to be repeated on the bind mount? do other options need to be repeated on the bind as well? i had thought they were inherited from the base mount.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-05 Thread Steve Langasek
The bind mounts would also need to be marked 'nobootwait'. This flag is not inherited. ** Changed in: mountall (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1115600] Re: nobootwait no longer averts waiting for fsck

2013-02-04 Thread Steve Langasek
Hi Greg, Could you please attach a full /etc/fstab that demonstrates this problem? ** Changed in: mountall (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.