I now can confirm your suspicion and reproduce it.
I have here a VM with Lucid-amd64 with a snapshot taken on Dec. 3rd an did following:
Boot VM
check 'cat /var/log/messages | grep orphan' -> no matches
wait ca. 5 minutes till pending updates are reported: 29 alltogether
install all updates with exception of libc-bin, libc-dev-bin, libc6, libc6-dev
system requests "reboot required", so
shutdwon
boot-up again
check 'cat /var/log/messages | grep orphan' -> no matches
install the remaining 4 libc-packages
no reboot requested by system!
This can be reproduced any time, I just have to revert to the machine's snapshot.
If you need further infomation collected, please let me know - it's really easy now.
Additional remarks:
a) I have purged plymouth completely by using a liberated mountall-package (otherwise I even would not have noticed that bug without watching the boot messages on tty1).
b) This did never happen with Debian-Squeeze - so it is Ubuntu specific
c) shutdown process here is extremely fast, generally 5 sec. or even less
@Paul
I now can confirm your suspicion and reproduce it.
I have here a VM with Lucid-amd64 with a snapshot taken on Dec. 3rd an did following:
Boot VM
check 'cat /var/log/messages | grep orphan' -> no matches
wait ca. 5 minutes till pending updates are reported: 29 alltogether
install all updates with exception of libc-bin, libc-dev-bin, libc6, libc6-dev
system requests "reboot required", so
shutdwon
boot-up again
check 'cat /var/log/messages | grep orphan' -> no matches
install the remaining 4 libc-packages
no reboot requested by system!
shutdown
boot-up again
cat /var/log/messages | grep orphan
Dec 17 12:16:44 lucid kernel: [ 2.976983] EXT3-fs: sda1: orphan cleanup on readonly fs
Dec 17 12:16:44 lucid kernel: [ 2.981618] EXT3-fs: sda1: 8 orphan inodes deleted
And as expected we get the orphaned inodes.
This can be reproduced any time, I just have to revert to the machine's snapshot.
If you need further infomation collected, please let me know - it's really easy now.
Additional remarks:
a) I have purged plymouth completely by using a liberated mountall-package (otherwise I even would not have noticed that bug without watching the boot messages on tty1).
b) This did never happen with Debian-Squeeze - so it is Ubuntu specific
c) shutdown process here is extremely fast, generally 5 sec. or even less