What Ingo said - for servers, not having a console progress bar is *terrible*,
since for servers we often aren't physically there. So even with e.g. remote
VNC access we get nothing but a blank screen and have no idea if it's actually
even doing a fsck, or locked up for some other reason.
My comment above was incorrect:
there is no more any output from regularly run fsck available during
boot on the console. - sorry.
It still shows up, the only difference:
it does not display partitions by device (/dev/sdaX), instead it displays the
label. That's why I overlooked it.
Is there
This bug was fixed in the package mountall - 2.15.3
---
mountall (2.15.3) lucid-proposed; urgency=low
[ Colin Watson ]
* Fix infinite loop when one of mountall's private mount options is
followed by a comma, and guard against other reasons why cut_options
might end up
I've verified this by the following:
## start instance of type m1.small (any instance type that has a ephemeral0
## will show it)
## ami-6c06f305 = ebs/ubuntu-lucid-10.04-i386-server-20100923
# ec2-run-instances ami-6c06f305 --instance-type t1.micro
# ssh to instance
$ sudo reboot # it took a
Ingo,
It doesn't seem likely that the changes made in 2.15.3 affected such output.
See the diff from 2.15.1 - 2.15.3 at [1]. I found that from [2]. The first
2 hunks of the mountall.c changes are the only changes made in 2.15.3 versus
2.15.2.
--
[1]
I did test 2.15.3 in Lucid-amd64 and observed (compared with 2.15.2):
there is no more any output from regularly run fsck available during boot on
the console. It just reports:
fsck from util-linux-ng 2.17.2
2.15.2 showed for every single device something like this:
fsck from util-linux-ng
Accepted mountall into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Branch linked: lp:ubuntu/lucid-proposed/mountall
--
mountall spins eating cpu when 'nobootwait' option exists in fstab followed by
a comma
https://bugs.launchpad.net/bugs/649591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Uploaded to lucid-proposed. Please test that build when it becomes
available and respond here with comments.
** Changed in: mountall (Ubuntu Lucid)
Assignee: Colin Watson (cjwatson) = Dustin Kirkland (kirkland)
** Changed in: mountall (Ubuntu Lucid)
Status: Triaged = In Progress
**
I did a local build of the proposed merge, and tested that it fixes the issue.
Additionally, I have a build pending in my ppa with that also.
This is ready for someone to sponsor to lucid-proposed, but I cannot do
the upload myself.
--
mountall spins eating cpu when 'nobootwait' option exists
** Branch linked: lp:~smoser/ubuntu/lucid/mountall/bug649591
--
mountall spins eating cpu when 'nobootwait' option exists in fstab followed by
a comma
https://bugs.launchpad.net/bugs/649591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Binary package hint: mountall
As reported at [1], mountall is eating cpu cycles on reboot of both
10.04 (images 20100923 and later) and 10.10.
I believe the issue is related to changes made under bug 634102.
Here is what happens:
- The images are
** Description changed:
Binary package hint: mountall
As reported at [1], mountall is eating cpu cycles on reboot of both
10.04 (images 20100923 and later) and 10.10.
I believe the issue is related to changes made under bug 634102.
Here is what happens:
- The images are
As pointed out in Eric Hammond's post, this bug can be fixed in a booted
instance with:
- sudo perl -pi -e 's/(nobootwait),(\S+)/$2,$1/' /etc/fstab
or, if you prefer sed:
- sudo sed -i 's/\(nobootwait\),\([^[:space:]]\+\)/\2,\1/' /etc/fstab
That will change:
/dev/sda2 /mnt auto
** Summary changed:
- mountall spins eating cpu when 'nobootwait' option exists in fstab
+ mountall spins eating cpu when 'nobootwait' option exists in fstab followed
by a comma
** Also affects: mountall (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu
** Branch linked: lp:ubuntu/mountall
--
mountall spins eating cpu when 'nobootwait' option exists in fstab followed by
a comma
https://bugs.launchpad.net/bugs/649591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package mountall - 2.19
---
mountall (2.19) maverick; urgency=low
* Fix infinite loop when one of mountall's private mount options is
followed by a comma, and guard against other reasons why cut_options
might end up comparing a zero-length option
17 matches
Mail list logo
