mountall calls mount -a for every mount
Bug #537135 reported by
Aron Griffis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: mountall
For example:
spawn: mount -n -a -t nfs -o remount,nolock 16.1.1.
I suspect that -a is a mistake. It's line 1702 in mountall.c from version 2.7
ProblemType: Bug
Architecture: amd64
Date: Thu Mar 11 01:31:28 2010
DistroRelease: Ubuntu 10.04
Package: mountall 2.7
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: mountall
Uname: Linux 2.6.32-15-generic x86_64
Changed in mountall (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package mountall - 2.10
---------------
mountall (2.10) lucid; urgency=low
* Rework the Plymouth connection logic; one needs to attach the client to
the event loop *after* connection otherwise you don't get disconnection
notification, and one needs to actually actively disconnect in the
disconnection handler.
* For safety and sanity reasons it becomes much simpler to create the
ply_boot_client when we connect, and free it on disconnection. Thus the
presence or not of this struct tells us whether we're connected or not.
LP: #524708.
* Flush the plymouth connection before closing it and exiting, otherwise
updates may be pending and the screen have messages that confuse people
while X is starting (like fsck at 90%). LP: #487744.
* Replace the modal plymouth prompt for error conditions with code that
continues working in the background while prompting. This most benefits
the old "Waiting for" message, which can now allow you to continue to
wait and it can solve itself. LP: #527666, #545435.
* Integrate fsck progress updates into the same mechanism.
* Allow fsck messages to be translated. LP: #390740.
* Change fsck message to be a little less alarming. LP: #545267.
* Add hard dependency on Plymouth; without it running, mountall will
ignore any filesystem which doesn't show up within a few seconds or that
fails to fsck or mount. If you don't want graphical splash, you simply
need not install themes.
* Improve set of messages seen with --verbose, and ensure all visible
messages are marked for translation. LP: #446592.
* Reduce priority of failed to mount error for remote filesystems since
we try again, and this just spams the console. LP: #504224.
* Keep hold of the dev_t when parsing /proc/self/ mountinfo, then after
mounting /dev (or seeing that it's mounted) create a quick udev rules
file that adds the /dev/root symlink to this device. LP: #527216.
* Do not try and update /etc/mtab when it's a symbolic link. LP: #529993.
* Remove odd -a option from mount calls, probably a C&P error from the
fsck code long ago. LP: #537135.
* Wait for Upstart to acknowledge receipt of events, even if we don't
hang around for them to be handled.
* Always run through try_mounts() at least once. LP: #537136.
* Don't keep mountall running if the only remaining unmounted filesystems
*
-- Scott James Remnant <email address hidden> Wed, 31 Mar 2010 19:37:31 +0100