I'm glad to see this is moving forward! Thanks Clint, Ingo and the rest
of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because
Clint,
I agree up to a certain point:
1) There is no obvious proof that anyone is doing anything with this, as
some of the other bugs mentioning this issue are over a year old. I
believe you, but some more active overview on what is being done would
be appreciated.
2) Although it is not necessar
Bug 348346 also talks about how a libc upgrade should restart init to
unload old libc to avoid remount root to read only issues. It appears to
not work though, and seeing the non-response from the package
maintainers (even after being marked critical), I have my doubts this
will be fixed anytime so
Debian doesn't do upstart yet I believe. Since upstart is the only
process left which keeps references to the old libc, that's probably
causing the issue. There is no apparent and proper way to restart
upstart after a libc upgrade.
--
You received this bug notification because you are a member of
It appears Bug #616287 is related to this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I opened Bug #672177 last month to see if this can be fixed. It's
currently assigned to the eglibc package. Unfortunately it doesn't seem
anyone is interested in resolving it. I'd like to stress that it appears
EVERYONE who installs 10.04 or 10.10 will have this issue eventually
when they update th
I still believe this has something to do with libc6. I only see this
issue after an upgrade of libc6, it appears upstart or sysvinit still
references the old version. The issue has been documented on the web a
few times, and whatever I do, this only happens after a libc6 upgrade.
Subsequent reboots
If this is 'how it should be'/accepted behavior, then something is
obviously wrong. Having filesystem issues right after a clean install
due to some libc upgrade is not acceptable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
@Clint Byrum - bug 603363 seems to talk about an issue where sshd is not
properly being stopped, this was fixed for maverick, but apparently not
for lucid. I ran lsof in the umountroot script, so right before the root
fs should be remounted read only. I don't think anything gets killed in
there bet
Thank you. It appears that this is somewhat similar to what happens in a
very old bug (188925). Not sure if this is some kind of regression or if
this is 'how things are supposed to be'. On reboot lsof only shows init
being in use, with some of the libraries (incl. libc6). So right now I
can only b
It appears my umount issue is caused by two things:
1) sshd no longer stops on lucid, due to an error in the upstart ssh.conf file
2) I did an upgrade of libc6, which caused the issue aswell
Atleast it looks like this is it for me :-)
--
umountfs doesn't cleanly unmount / on reboot
https://bugs
Also - this only happens once after upgrading, after that, reboots work
just fine without causing mount to fail on trying to unmount a busy root
filesystem.
--
libc6 upgrade causes umount to fail on shutdown
https://bugs.launchpad.net/bugs/672177
You received this bug notification because you are
--
libc6 upgrade causes umount to fail on shutdown
https://bugs.launchpad.net/bugs/672177
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
https://lists.ubuntu.com/mailman/listinf
Public bug reported:
On a clean install of Ubuntu 10.04.1, after upgrading the offer libc6
upgrade, on the next reboot the root fs can't be properly unmounted
(mount: / is busy). This causes fsck to run on boot and of course some
minor issues with the filesystem. This might not be a problem with l
Good question. I'm experiencing some issues with the root filesystem
(only one fs on this system) being busy on reboots, running a lsof from
umountroot shows that sshd is still running, which could be a reason for
the root fs to be busy. How can this be fixed properly in lucid?
--
sshd never stop
I'm seeing the same on a CLI only install (Ubuntu 10.04 server cd /
minimal install). This is actually delaying the installation of a new
server for me, since I'm afraid of data corruption. It appears to be
what Clint describes, I do not see any issues with a single root
partition and swap, the iss
*** This bug is a duplicate of bug 526416 ***
https://bugs.launchpad.net/bugs/526416
** This bug has been marked a duplicate of bug 526416
package drbd8-source 2:8.3.3-0ubuntu2 failed to install/upgrade: drbd8
kernel module failed to build
--
8.3.3 incompatible with lucid kernel (2.6.32)
Public bug reported:
The current version of the drbd8-utils/source package appears to be
incompatible with the kernel which will ship with lucid. The latest
release (8.3.7) is reported to have support for kernel 2.6.32. Is it
possible to make sure this package gets updated to 8.3.7?
See also debi
18 matches
Mail list logo
