So I got another step further: the fs corruption happens definitely upon shutdown:
1. upgraded libc6 and also forced ureadahead to reprofile on reboot 'rm /var/lib/ureadahead/pack*' -> orphande inodes 2. Upgraded libc6 and afterwards shut down the VM. Booted up again fronm a Knoppix6.1 DVD and checked filesystem: -> 8 corrupted inodes (I type and translate, as I have a screenshot only): fsck -f /dev/hda1 fsck 1.41.3 (12-Oct-2008) /dev/hda1: replaying journal cleaning orphaned Inode 185586 (uid=0, gid=0, mode00100644, size 51712) ... 7 similar lines, all uid0gid=0 follow ... Pass 1: Checking Inodes Pass 2: ... So this definitely indicates that the bug is caused by shutdown. It shows that Journal had not been commited. So my guess is, that upgrading libc6 is just one (reliable) triger for the root cause "filesystem not cleenly umounted". There may be othe occasion causing the same or even more severe corruptions. libc6 is just fine for tracing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/616287 Title: umountfs doesn't cleanly unmount / on reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
