The best way to try and figure out what is causing this is to modify
/etc/init.d/umountroot and right before the umount's, add
/usr/bin/lsof -n /saved.root.lsof
sync
This will save a listing of all opened files and which processes have
them open. Things marked as 'deleted' in this list are
On 12/20/2011 09:47 AM, Clint Byrum wrote:
The best way to try and figure out what is causing this is to modify
/etc/init.d/umountroot and right before the umount's, add
/usr/bin/lsof -n /saved.root.lsof
sync
This will save a listing of all opened files and which processes have
them
Clint, can you give me the exact location for
/usr/bin/lsof -n /saved.root.lsof
sync
in /etc/init.d/umountroot? So far I not been successful in creating
'/saved.root.lsof'
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
Nevermind. Got it working.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot be
restarted
To manage
@Clint: it's back. On Natty 11.04 I am getting unclean inodes again. I notice
a single inode in dmesg after every boot:
$ cat /var/log/dmesg.0 | grep orphan
[4.470372] EXT4-fs (sda1): orphan cleanup on readonly fs
[4.470443] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
Excerpts from chtnh's message of Sat Jul 23 04:41:01 UTC 2011:
I'm new in Ubuntu (10.10) and in Lauchpad, and I have this bug. I don't
understand how you fix it, as there is fix released. Can someone explain
me, please?
There are other bugs that sometimes cause an unclean shutdown, this one
I'm new in Ubuntu (10.10) and in Lauchpad, and I have this bug. I don't
understand how you fix it, as there is fix released. Can someone explain
me, please?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu17.1
---
sysvinit (2.87dsf-4ubuntu17.1) lucid-proposed; urgency=low
* debian/initscripts/etc/init.d/umountroot: Improve handling of
respawn of init: we now wait for inits map file to change. If this
doesn't happen
This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu19.1
---
sysvinit (2.87dsf-4ubuntu19.1) maverick-proposed; urgency=low
* debian/initscripts/etc/init.d/umountroot: Improve handling of
respawn of init: we now wait for inits map file to change. If this doesn't
Any testers? This is blocking another SRU right now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot be
Maverick:
$ dmesg | grep orphan
[7.716966] EXT4-fs (sda5): orphan cleanup on readonly fs
[7.716978] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode
5899558
[7.717070] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode
5899556
[7.717087] EXT4-fs
natty:
$ dmesg | grep orphan
$ apt-cache policy sysvinit-utils
sysvinit-utils:
Installed: 2.87dsf-4ubuntu23
Candidate: 2.87dsf-4ubuntu23
Version table:
*** 2.87dsf-4ubuntu23 0
500 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status
--
You
lucid:
$ dmesg | grep orphan
$ apt-cache policy sysvinit-utils
sysvinit-utils:
Installed: 2.87dsf-4ubuntu17.1
Candidate: 2.87dsf-4ubuntu17.1
Version table:
*** 2.87dsf-4ubuntu17.1 0
500 http://archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
100 /var/lib/dpkg/status
@Martin: checking maverick on another system:
$ dmesg | grep orphan
[ 13.879321] EXT4-fs (sda1): orphan cleanup on readonly fs
[ 13.879356] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode
263685
[ 13.879661] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode
NoOp, thanks so much for doing these tests!
There are a couple of other bugs that cause this to happen if you have some
other services
installed. Some of these are fixed in uploads waiting on this SRU, and some in
yet to be
SRU'd fixes (which is why natty seems to always work).
Specifically,
Clint, I did have portmap running stopped prior on this test:
$ sudo service portmap stop
$ sudo service portmap status
portmap stop/waiting
$ sudo -i
# service portmap status
portmap stop/waiting
# apt-get install --reinstall libc6 shutdown -r now
on reboot
$ dmesg | grep orphan
again EXT4-fs
Booted to lucid (the one from comment #110 that showed no errors.
Install portmap repeated the test on that machine:
$ dmesg | grep orphan
[3.676128] EXT4-fs (sdb1): orphan cleanup on readonly fs
[3.676159] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode
193222
[
Some nitpicks about the patch:
- patch ordering in series
- target is {lucid,maverick}-proposed
- changelog missing bug references.
- version 2.87dsf-4ubuntu18 already exists in maverick, can't be used for
lucid-updates
- maverick debdiff doesn't apply, as it wasn't done against -updates.
Accepted sysvinit 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!
** Changed in: sysvinit (Ubuntu Lucid)
Accepted sysvinit into maverick-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!
** Changed in: sysvinit (Ubuntu
James' patch appears to have been applied in natty now, so I'm closing
this bug task. Please reopen if this was incorrect.
sysvinit (2.87dsf-4ubuntu20) natty; urgency=low
[ Michael Vogt ]
* debian/patches/100_fix_ftbfs_enoioctlcmd.patch:
- cherry pick upstream fix for missing
This is a bug fix, can happen after FF, and isn't an a3 release blocker.
** Changed in: sysvinit (Ubuntu Natty)
Milestone: natty-alpha-3 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
** Changed in: sysvinit (Ubuntu Natty)
Importance: Undecided = High
** Changed in: sysvinit (Ubuntu Natty)
Milestone: None = natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
On 16.02.2011 00:25, Clint Byrum wrote:
There are also a couple more bugs
covering daemons that need to be shutdown, namely, sshd and portmap.
Clint,
the portmap Bug #711425 you filed has not got any attention yet, it's
still undecided and unassigned - does nobody care?
--
You received this
Well it is not yet fixed for 10.04 with the 'proposed' updates. Tonight
just rebooted after updates to kernal 2.6.32-29 and guess what? Yes, my
syslog contained the following sort of message:
Feb 15 21:45:24 paul-ubuntu kernel: [2.341704] EXT4-fs (sda5): 4
orphan inodes deleted
So is
On Tue, 2011-02-15 at 21:51 +, Paul Crawford wrote:
Well it is not yet fixed for 10.04 with the 'proposed' updates. Tonight
just rebooted after updates to kernal 2.6.32-29 and guess what? Yes, my
syslog contained the following sort of message:
Feb 15 21:45:24 paul-ubuntu kernel: [
I'm targetting the sysvinit bug task for lucid to 10.04.3, but it should
be done well before then.
** Changed in: sysvinit (Ubuntu Lucid)
Importance: Undecided = Critical
** Changed in: sysvinit (Ubuntu Lucid)
Milestone: None = ubuntu-10.04.3
--
You received this bug notification
Will this bug also be fixed for lucid the LTS version?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot be
This bug was fixed in the package upstart - 0.6.7-7
---
upstart (0.6.7-7) natty; urgency=low
* Re-add upstream r977 to allow proper re-exec on shutdown (LP: #672177)
* debian/control: adding Breaks on eglibc version that disables
telinit u to avoid accidentally installing a
This bug was fixed in the package eglibc - 2.12.1-0ubuntu10.2
---
eglibc (2.12.1-0ubuntu10.2) maverick-proposed; urgency=low
[ Clint Byrum ]
* do not run 'telinit u' on upgrade, as this will break upstart.
touch /var/run/init.upgraded instead, which will force a re-exec just
Would bug #711601 be caused by the Breaks: field mentioned by Clint?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init
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
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown
Hi Clint,
me just came up an idea how we could make this bug hunting more
systematic and thoroughly. Up to now we just found some conditions in
which shutdown process fails (sshd and portmap). Who tells us that there
aren't more daemons which get hardly killed upon shutdown/reboot?
So, if for
Attached is a patch to sysvinit (from which the initscripts binary
package is generated) which appears to fix the immediate problem.
The patch waits for up to 5 seconds for init (upstart) to re-exec. If
after this time init has not re-execed, we continue to unmount as
before. (In testing, init
Equivalent sysvinit patch for Maverick.
** Patch added:
maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.diff
Equivalent sysvinit patch for Natty.
** Patch added:
natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff
https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824656/+files/natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff
--
First: Many great thanks to you all for your work.
Now, the updates just got released to Maverick.
How do I verify that it works?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
James,
did you already upload to proposed (so we'll get binaries tomorrow)?
If not, could you be so kind and compile a 'Lucid-amd64 binary' for testing
here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
I just saw it is a addition to 'umountroot', so I could copy+past form
your diff - right?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on
@ Jimmy
How do I verify that it works?
when system is up and running, issue following command as root and confirm the
install when requested:
'apt-get install --reinstall libc6 shutdown -r now'
after system has rebooted, check for orphaned inodes with this command (works
as user):
@ James,
I verified your patch in Lucid-amd64 (by manually inserting your lines of code)
and can confirm: *it works*!
(apart from the portmap and rpc.statd issue, whuich still persists of course).
I used Clints proposal inserting these 2 lines after the mount commands:
/usr/bin/lsof -n |
Additional remark: I did not observe any noticeble delay of shutdown
with the patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on
Addition (works for me):
/usr/bin/lsof -n | grep DEL /lsof.out 21
sleep 15
greps all the open files/libs - if there are any - and writes the information
to disk.
If there are none one just gets an error message that could not write to ro
filesystem.
--
You received this bug
I now de-installed portmap+nfs-common and did install openssh-server:
*Only when* I replace the line in /etc/init/ssh.conf by:
stop on runlevel [!2345]
all is fine with James' patch included!
With the original line
stop on runlevel S
I get a lot of open files, like this:
sshd 1385
Bad news there: I'm afraid that we've already had to entirely freeze
updates for 10.04.2 in order that we can get certification done in time;
unfortunately that's a rather time-consuming process and needs a couple
of weeks of clearance. I expect that 10.04.3 won't be a problem,
though.
--
You
... freeze updates for 10.04.2 in order that we can get certification
done
That means we get certified BUGS - and that 10 months after release!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
I'm afraid there's no point railing about it here - we're already
committed to the date and it would be a colossal rearrangement of many
people's schedules to change it at this point. As I say, sorry, and we
should be able to get this nailed down for .3.
--
You received this bug notification
At least certified bugs can be documented, with certified workarounds.
On Wed, Feb 2, 2011 at 2:05 PM, ingo 672...@bugs.launchpad.net wrote:
... freeze updates for 10.04.2 in order that we can get certification
done
That means we get certified BUGS - and that 10 months after release!
--
Verification for Lucid for eglibc and upstart.
I've verified that the package upgrades correctly from a default Lucid
installation and that after the installation the system reboots, that X
and the network are working. If there are specific verifications to do,
let me known.
Marking as
On Sun, 2011-01-23 at 12:39 +, ingo wrote:
Observed just another oddity, probably a separate bug in mountall?
I tried to mount the / filesystem (ext3) in journal mode to see if this
improves the situation by adding the option to /etc/fstab:
data=journal,erros=remount-ro
But that
On Sun, 2011-01-23 at 11:50 +, ingo wrote:
Sorry, but I can't reproduce it now, getting still 4 orphaned inodes.
Can I insert some lines to log which libs are still in use?
Yes, you can put this just after the remounts:
lsof -n | grep DEL
sleep 10
Which will give you 10 seconds to view
This bug was fixed in the package eglibc - 2.11.1-0ubuntu7.8
---
eglibc (2.11.1-0ubuntu7.8) lucid-proposed; urgency=low
[ Matthias Klose ]
* Fix issue #12077, __strncmp_ssse3 can segfault when it over-reads
its buffer. LP: #702190.
[ Clint Byrum ]
* do not run 'telinit
This bug was fixed in the package upstart - 0.6.5-8
---
upstart (0.6.5-8) lucid-proposed; urgency=low
* Re-add upstream r977 to allow proper re-exec on shutdown (LP: #672177)
* debian/control: adding Breaks on eglibc version that disables
telinit u to avoid accidentally
This bug was fixed in the package upstart - 0.6.6-4
---
upstart (0.6.6-4) maverick-proposed; urgency=low
* Re-add upstream r977 to allow proper re-exec on shutdown (LP: #672177)
* debian/control: adding Breaks on eglibc version that disables
telinit u to avoid accidentally
you can put this just after the remounts:
lsof -n | grep DEL
sleep 10
*Lucid-amd64*
I did so (with new libc6 and upstart from Lucid-proposed installed) and found
something new:
it's the NFS which makes trouble. Portmap and statd are still running!
(I just list the essential information here,
BTW: just some minutes ago nwe 'libc6' and 'upstart' was offered as an
official update for Lucid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to
I now stopped portmap by '/etc/init.d/portmap stop' prior to executing
'apt-get install --reinstall libc6 shutdown -r now'
and got just the messages
init: Re-executing /sbin/init
mount: / is busy
but no more output from 'lsof'
--
You received this bug notification because you are a member
** Changed in: eglibc (Ubuntu Lucid)
Assignee: (unassigned) = Bobby A. Callender (bcallender)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to
and no more any orphaned inodes (with portmap stopped before)!
Congratulations, you are approaching the solution!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade
On Tue, 2011-02-01 at 16:17 +, ingo wrote:
you can put this just after the remounts:
lsof -n | grep DEL
sleep 10
*Lucid-amd64*
I did so (with new libc6 and upstart from Lucid-proposed installed) and found
something new:
it's the NFS which makes trouble. Portmap and statd are still
But there is no way to codify that point in the shutdown into the
upstart job, which I suspect is why it has no stop on. I believe the
proper way to handle this is to have a matching event to
remote-filesystems , unmounted-remote-filesystems, with which to stop
on, and then have umountnfs.sh
I just checked:
portmap is not included in nfs-common, it's a separate package. But it
is refereced by nfs-common as required!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
On Tue, 2011-02-01 at 20:23 +, ingo wrote:
But there is no way to codify that point in the shutdown into the
upstart job, which I suspect is why it has no stop on. I believe the
proper way to handle this is to have a matching event to
remote-filesystems , unmounted-remote-filesystems,
Puh, by and by I understand why Ubutu is blamed for use on servers.
Do you see any chance to get that mess cleaned up in Lucid?
(Squeeze is beeuing released soon)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
On Tue, 2011-02-01 at 21:32 +, ingo wrote:
Puh, by and by I understand why Ubutu is blamed for use on servers.
Do you see any chance to get that mess cleaned up in Lucid?
(Squeeze is beeuing released soon)
I don't know if I'd call it a mess at this point. The shutdown will
certainly be
Now (after a while) I've gotten through reading this bug.
I have just updated my server, it now runs 10.04.2. Does this mean it
has no issues? It's a non-critical server I access remotely. should I
care at all, or just wait for things to get even better?
On my laptop I see upstart as
Forgot: My laptop runs Maverick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot be
restarted
--
On Tue, 2011-02-01 at 23:06 +, Jimmy Merrild Krag wrote:
Now (after a while) I've gotten through reading this bug.
I have just updated my server, it now runs 10.04.2. Does this mean it
has no issues? It's a non-critical server I access remotely. should I
care at all, or just wait for
** Changed in: sysvinit (Ubuntu Maverick)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: sysvinit (Ubuntu Maverick)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
I don't understand anything of the shutdown procedure. I found this bug report
because I recognized orphaned inodes in my / home partition after shutdown.
(Ubuntu 10.04 on 32 and 64bit hardware)
My question is:
When this bug (orphaned inodes) will be fixed for the /-partition, will it also
@Zippo,
it is really a sad story with LTS-Lucid. I really don't understand how
such a buggy release could pass QC (if there is any?). I.e. today there
came in an update of openSSH in Lucid, and still the old bug in the
upstart-script '/etc/init/ssh.conf' (stop on runlevel S) is not fixed.
Set it
ingo: that's the way the Ubuntu release process works, I'm sorry that
this is a surprise to you
On Mon, Jan 24, 2011 at 1:00 PM, ingo 672...@bugs.launchpad.net wrote:
@Zippo,
it is really a sad story with LTS-Lucid. I really don't understand how
such a buggy release could pass QC (if there is
@56: I dont think so. The release process is a Canonical special
feature. These processes are not written in stone and can be changed
by the people working for Canonical. Maybe i should write: Must be
redefined by the people working for Canonical.
--
You received this bug notification because
Clint, seems you are doing an excellent job and I am confident it gets
fixed finally!
Your proposal works, however only if I modify /etc/init.d/umountroot
this way:
[ -f /var/run/init.upgraded ] telinit u sleep 1 || :
it does *not* work, if I place the sleep in a separate line like
Sorry, but I can't reproduce it now, getting still 4 orphaned inodes.
Can I insert some lines to log which libs are still in use?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
Observed just another oddity, probably a separate bug in mountall?
I tried to mount the / filesystem (ext3) in journal mode to see if this
improves the situation by adding the option to /etc/fstab:
data=journal,erros=remount-ro
But that results in boot process stalling with / filesystem mounted
Thanks for Lucid-fix. I did immediately test with new 'libc6' and
'upstart' from Lucid-proposed:
1. just new 'libc6' - does not change anything (8 orphaned inodes after
reboot).
2. + new 'upstart' - gives 1 orphaned inode after reboot.
3. new ('libc6' + 'upstart'), 'apt-get install --reinstall
On Sat, 2011-01-22 at 11:50 +, ingo wrote:
Thanks for Lucid-fix. I did immediately test with new 'libc6' and
'upstart' from Lucid-proposed:
1. just new 'libc6' - does not change anything (8 orphaned inodes after
reboot).
2. + new 'upstart' - gives 1 orphaned inode after reboot.
3.
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/upstart/restore-re-exec
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because
** Branch linked: lp:~clint-fewbar/ubuntu/maverick/upstart/restore-re-
exec
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because
Accepted eglibc 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!
** Changed in: eglibc (Ubuntu Lucid)
Accepted upstart 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!
** Changed in: upstart (Ubuntu Lucid)
** Branch linked: lp:ubuntu/lucid-proposed/upstart
** Branch linked: lp:ubuntu/maverick-proposed/upstart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes
** Also affects: eglibc (Ubuntu Natty)
Importance: Critical
Status: Fix Released
** Also affects: sysvinit (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Natty)
Importance: Critical
Assignee: Clint Byrum (clint-fewbar)
Status:
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/upstart/re-exec-plus-
ptrace
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/upstart/wait-for-re-
exec-semaphores
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on
Added sysvinit, as umountroot needs to wait for the upstart re-exec to
actually happen before moving forward (can do this in telinit as well,
but given the design to use SIGTERM and have no way to signal back to
telinit that the re-exec is done, its much simpler to have umountroot
just watch for a
** Changed in: upstart (Ubuntu Lucid)
Status: New = Triaged
** Changed in: upstart (Ubuntu Maverick)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Today again after security update for 'udev' and reboot: 1 orphaned
inode.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because
** Also affects: eglibc (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: eglibc (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Maverick)
Today another libc6 upgrade (security) came in. This is Lucid's file
system just after shutdown:
# fsck -f /dev/sda6
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
Lucid: stelle das Journal wieder her
Bereinige verwaist Inode 310667 (uid=0, gid=0, mode=0100644, size=51712)
Bereinige
I can confirm that on Ubuntu Lucid 64bit.
Bug still in place...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init
This is funny because I reported this bug in the ubuntu forums in 2007
but i was ignored and it was blamed on the user (not surprised)
http://ohioloco.ubuntuforums.org/showthread.php?t=645429
(this is my original post from December 2007 same bug)
--
You received this bug notification because
This bug was fixed in the package eglibc - 2.12.1-0ubuntu12
---
eglibc (2.12.1-0ubuntu12) natty; urgency=low
* do not run 'telinit u' on upgrade, as this will break upstart.
touch /var/run/init.upgraded instead, which will force a re-exec just
before remounting root
** Changed in: eglibc (Ubuntu)
Assignee: Clint Byrum (clint-fewbar) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on
Hi Clint,
thanks for fast fix - but unfortunately only in Natty which is still in
development. This bug was reported for *Lucid*, which in terms of
service will even survive Natty. When will that be fixed and who cares?
--
You received this bug notification because you are a member of Ubuntu
On Wed, 2011-01-05 at 21:31 +, ingo wrote:
Hi Clint,
thanks for fast fix - but unfortunately only in Natty which is still in
development. This bug was reported for *Lucid*, which in terms of
service will even survive Natty. When will that be fixed and who cares?
Hi Ingo. This is the
** Branch linked: lp:~clint-fewbar/ubuntu/natty/eglibc/no-telinit-u
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init
The test failures that I saw were caused by running the build step as
root. I didn't think sbuild did that, but apparently it does. When I
build inside a clean chroot as non-root the build seems to work fine.
I will file the merge proposal then and also do the glibc change.
** Changed in:
Yes, I know how to drive bzr and dpkg ;-)
My point is that if you do that diff, the only occurrence of SIGTERM
is in the code for the upstart/udev bridge, that patch doesn't add any
handling to upstart itself.
Scott
On Wed, Dec 29, 2010 at 6:54 AM, Clint Byrum cl...@fewbar.com wrote:
On Wed,
1 - 100 of 109 matches
Mail list logo
