PDA

View Full Version : [ubuntu] 9.10/amd64 server ext4 orphans after dist-upgrade



tr1976
January 18th, 2010, 08:55 AM
Hi all,

I have installed Ubuntu 9.10-server (amd64) two times and I seem to always get ext4 orphans
on the root partition filesystem after I run "apt-get update; apt-get dist-upgrade; reboot".

I have two identical SATA drives and md0 is a RAID-1 partition.

I don't see any other problems from disk drives. I have ran bonnie++ and rebooted the
system several times. It seems that those orphans are caused by updating some package(s).

So I guess there is a bug somewhere. Should I do something or can I assume that the
file system is fine and keep running the system?

Thanks,
Teemu

Jan 18 08:34:15 server kernel: [ 4.313132] EXT4-fs (md0): INFO: recovery required on readonly filesystem
Jan 18 08:34:15 server kernel: [ 4.313136] EXT4-fs (md0): write access will be enabled during recovery
Jan 18 08:34:15 server kernel: [ 4.325094] EXT4-fs (md0): barriers enabled
Jan 18 08:34:15 server kernel: [ 4.707248] kjournald2 starting: pid 481, dev md0:8, commit interval 5 seconds
Jan 18 08:34:15 server kernel: [ 4.707260] EXT4-fs (md0): delayed allocation enabled
Jan 18 08:34:15 server kernel: [ 4.707265] EXT4-fs: file extents enabled
Jan 18 08:34:15 server kernel: [ 4.709322] EXT4-fs: mballoc enabled
Jan 18 08:34:15 server kernel: [ 4.709334] EXT4-fs (md0): orphan cleanup on readonly fsJan 18 08:34:15 server kernel: [ 4.709340] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 132879
Jan 18 08:34:15 server kernel: [ 4.709417] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 798Jan 18 08:34:15 server kernel: [ 4.709434] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 796
Jan 18 08:34:15 server kernel: [ 4.724329] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 594Jan 18 08:34:15 server kernel: [ 4.724359] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 592
Jan 18 08:34:15 server kernel: [ 4.724381] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 590
Jan 18 08:34:15 server kernel: [ 4.724402] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 589
Jan 18 08:34:15 server kernel: [ 4.724435] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 583
Jan 18 08:34:15 server kernel: [ 4.724489] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 318
Jan 18 08:34:15 server kernel: [ 4.724511] EXT4-fs (md0): 9 orphan inodes deleted
Jan 18 08:34:15 server kernel: [ 4.724515] EXT4-fs (md0): recovery complete
Jan 18 08:34:15 server kernel: [ 5.078841] EXT4-fs (md0): mounted filesystem with ordered data mode

mikechant
July 10th, 2010, 12:49 PM
I'm getting something similar on 10.4 - just updated all packages via synaptic and got 8 orphan inodes reported after clean shutdown and reboot. I've had this twice since upgrading to 10.4 from 9.04. Not a server install.

graytron
July 29th, 2010, 02:45 PM
I can confirm that this same problem still exists in Ubuntu 10.04 LTS Server Edition (Lucid Lynx) AMD64.

The system has 6 software RAID-1 partitions configured as follows.

/dev/md0 -> /
/dev/md1 -> swap
/dev/md2 -> /tmp
/dev/md3 -> /usr
/dev/md4 -> /var
/dev/md5 -> /home

After aptitude update and aptitude full-upgrade today, the system was rebooted (sudo shutdown -r now), and /var/log/syslog reported 13 orphan inodes on the root partition md0.

Jul 29 13:17:43 clu kernel: [ 6.410024] EXT4-fs (md0): INFO: recovery required on readonly filesystem
Jul 29 13:17:43 clu kernel: [ 6.410028] EXT4-fs (md0): write access will be enabled during recovery
Jul 29 13:17:43 clu kernel: [ 7.419228] EXT4-fs (md0): orphan cleanup on readonly fs
Jul 29 13:17:43 clu kernel: [ 7.419234] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 266
Jul 29 13:17:43 clu kernel: [ 7.419288] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5698
Jul 29 13:17:43 clu kernel: [ 7.419306] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5695
Jul 29 13:17:43 clu kernel: [ 7.419316] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5694
Jul 29 13:17:43 clu kernel: [ 7.419326] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5693
Jul 29 13:17:43 clu kernel: [ 7.419337] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5690
Jul 29 13:17:43 clu kernel: [ 7.419346] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5688
Jul 29 13:17:43 clu kernel: [ 7.419355] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5686
Jul 29 13:17:43 clu kernel: [ 7.419364] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5685
Jul 29 13:17:43 clu kernel: [ 7.419374] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5682
Jul 29 13:17:43 clu kernel: [ 7.419383] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5681
Jul 29 13:17:43 clu kernel: [ 7.419392] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5679
Jul 29 13:17:43 clu kernel: [ 7.419419] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5674
Jul 29 13:17:43 clu kernel: [ 7.419429] EXT4-fs (md0): 13 orphan inodes deleted
Jul 29 13:17:43 clu kernel: [ 7.419431] EXT4-fs (md0): recovery complete
Jul 29 13:17:43 clu kernel: [ 7.453755] EXT4-fs (md0): mounted filesystem with ordered data mode

Attached are full syslogs for before and after the reboot.

This is very worrisome indeed. Until a fix is delivered, I suggest that people who plan to use software RAID on Linux do not install Ubuntu, so not to risk losing their data because of a corrupted filesystem.

Its really nice that a computer boots and shuts down quickly, but not when it does so at the expense of stability and reliability.

Unless a bug has been filed already, I think one should be opened now. Anyone?

graytron
November 4th, 2010, 10:01 PM
This problem seems to have been fixed in Ubuntu.