Comment 23 for bug 1061639

watgrad (watgrad) wrote :

I also am concerned about this hidden bug - I only discovered there was an issue when I noticed that boot times were longer than normal. I have converted all my main computers to 12.10 64 bit...
They all show this behaviour with messaged like:
[ 1.111309] EXT4-fs (sdb1): INFO: recovery required on readonly filesystem
[ 1.111314] EXT4-fs (sdb1): write access will be enabled during recovery
...
[ 2.127937] EXT4-fs (sdb1): orphan cleanup on readonly fs
[ 2.127946] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148324
[ 2.128033] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148284
[ 2.128042] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 30148298
[ 2.128057] EXT4-fs (sdb1): ext4_orphan_cleanup: deleting unreferenced inode 44828301
[ 2.128091] EXT4-fs (sdb1): 4 orphan inodes deleted
[ 2.128093] EXT4-fs (sdb1): recovery complete

So I understand that this could lead to data loss? ...corrupt file system? I have tried to follow yota's suggested fix, but could not get that to work. On one laptop (macbookpro7,1 dual boot) shutting down networking before shutting down the computer stops the behaviour - but this is not true for the desktop systems (win7 dual boot).

The bug message says 'fix released' - how to I get and apply this fix? (I already have the rec version of ifupdown...)