> This bug was fixed in the package util-linux - 2.16-1ubuntu6
I just want to point out that this means it hasn't been fixed for Karmic
which is on 2.16-1ubuntu5 - am I right? Any chance of backporting the
fix?
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
It was a bad idea to introduce this change. Just cost me hours to find
out what was wrong with a production server and I still have no fix.
Using the bootwait option does not work, because the mount command
doesn't know about this option. Breaking hundreds of thousands of
systems is not acceptable.
This change has nothing to do with disk encryption.
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Guess not. Apparently people encrypting their disk are so far from
mainstream that it just doesn't make business sense to support those
users of the current release.
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you
Is util-linux going to be fixed in karmic too?
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug was fixed in the package util-linux - 2.16-1ubuntu6
---
util-linux (2.16-1ubuntu6) lucid; urgency=low
* mount/fstab.5: document the bootwait, nobootwait, showthrough
and optional mount options accepted by mountall.
* mount/mount.c: don't pass the above options to moun
We don't ask to wait for all the possible partitions
We ask for :
- no errors due to _UNDOCUMENTED_ bootwait option in /etc/fstab
- waiting for _LOCAL_ filesystem until fsck is finished at least a message in a
popup or CTRL-C to interrupt fsck ala debian old-fashion. It is the user
responsabilit
Scott,
Waiting for all filesystems is a problem for anyone:
- who uses NM to bring up their network at login time and has a network
filesystem configured in /etc/fstab
- who has an old and no longer applicable fstab entry that they haven't
cleaned up
- who has a custom fstab entry for any so
Good news for Lucid, but in the meantime what is the solution with
Karmic to have a system that waits for my filesystems to be checked ?
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you are a member of Ubuntu
Bugs,
For lucid, we've reverted to again waiting for all filesystems so the
bootwait option has been removed (all fstab entries act as if it was
there).
Leaving this bug open to remind me that there's still the "showthrough"
and "optional" options that util-linux's mount should ignore (generally
only us
I am not sure it is the same problem, but when I add "bootwait" in fstab
for my data (which is not /home) partition, the system won't boot at
all, it hangs somewhere during the process. Considering my
configuration, this bug is blocking for me.
--
"bootwait" in fstab causes mount problems
https:/
** Changed in: mountall (Ubuntu)
Status: Confirmed => Triaged
** Package changed: mountall (Ubuntu) => util-linux (Ubuntu)
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is a mountall bug.
mountall need to be fixed properly, and not mess-up fstab.
** Package changed: util-linux (Ubuntu) => mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: Triaged => Confirmed
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/47996
In my case, I am affected by this with a separate /home and /tmp
partition. I would think you could assume that things like /home /usr
and /tmp... maybe even /opt ought to hang the boot process. I grant you,
if you have /big-movies or something maybe that would be ok.
But certainly at least gdm/kd
How importance "LOW" ?
Are you mad ?
Currently servers boot without waiting for all partitions , and this cannot be
fixed, even by adding ugly workaround in fstab.
Mounting filesystems and /etc/fstab are not toys for kids. This is
CRITICAL
--
"bootwait" in fstab causes mount problems
https://b
see also https://bugs.launchpad.net/debian/+source/upstart/+bug/490746
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
It would be better to follow Ubuntu/Canonical policy to work with
upstrean (as recommended by M.Shuttleworth himself) and to have the
changes integrated in the package, with adequate documentation in the
manpages.
--
"bootwait" in fstab causes mount problems
https://bugs.launchpad.net/bugs/479965
We probably need to patch util-linux's mount to ignore the bootwait,
nobootwait and showthrough options ;-)
** Package changed: mountall (Ubuntu) => util-linux (Ubuntu)
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Low
** Changed in: util-linux (Ubuntu)
Status: New => Tri
18 matches
Mail list logo
