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
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
Bugs, which is subscribed to Ubuntu.
Nevermind. Got it working.
--
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 init cannot be
restarted
To manage notifications
@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
@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
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.
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
Bugs, which is subscribed to Ubuntu.
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
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
[
Any testers? This is blocking another SRU right now.
--
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 init cannot be
restarted
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
[
Excerpts from NoOp's message of Thu Apr 14 21:43:19 UTC 2011:
Rebooted then repeated the test, only this time I also check $ dmesg |
grep orphan before running the test:
$ dmesg | grep orphan
$
Now run the test:
$ dmesg | grep orphan
$
Would you like me to reinstall nfs-common*
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
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
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.
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
Bugs, which is subscribed to Ubuntu.
** 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.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
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
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
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
Will this bug also be fixed for lucid the LTS version?
--
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 init cannot be
restarted
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 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!
--
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown because init cannot
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown
@ 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
Title:
libc6 upgrade causes umount to fail on shutdown
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672177
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
1 - 100 of 219 matches
Mail list logo
