Arch Linux

tcn

Member

Registered: 2011-09-30

Posts: 86

ext4 orphan inodes - problem or false positive?

Hi!

Not an arch-specific but general ext fs (actually QNAP) question. Hope for the expertise abound here. I've been personally on btrfs for many years and haven't kept track with ext and it's potential quirks.

I got this when attaching a pretty new Crucial MX500 drive via USB:

[9240426.485998] EXT4-fs (sde1): Cannot turn on journaled quota: error -2
[9240426.492963] EXT4-fs error (device sde1): ext4_orphan_get:1179: comm mount: bad orphan inode 23261187
[9240426.502525] ext4_test_bit(bit=2, block=372178945) = 0
[9240426.507763] EXT4-fs (sde1): recovery complete
...
[9240827.404827] EXT4-fs (sde1): Mount option "noacl" will be removed by 3.5
[9240827.404827] Contact linux-ext4@vger.kernel.org if you think we should keep it.
[9240827.404827] 
[9240828.059396] EXT4-fs (sde1): warning: mounting fs with errors, running e2fsck is recommended
[9240828.075257] ext4_init_reserve_inode_table0: sde1, 14905
[9240828.080637] ext4_init_reserve_inode_table2: sde1, 14905, 0, 0, 4096
[9240828.087667] EXT4-fs (sde1): Errors on filesystem, clearing orphan list.
[9240828.087667] 
[9240828.096071] EXT4-fs (sde1): recovery complete
[9240828.100602] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,data_err=abort,delalloc,nopriv,nodiscard,noacl
[9240835.930472] ---- NAS_Disk_Hot_Add(enc_id=33, port_id=1) finished.
[9240989.986787] EXT4-fs (dm-21): Mount option "noacl" will be removed by 3.5
[9240989.986787] Contact linux-ext4@vger.kernel.org if you think we should keep it.
[9240989.986787] 
[9240990.118793] ext4_init_reserve_inode_table0: dm-21, 24576
[9240990.124259] ext4_init_reserve_inode_table2: dm-21, 24576, 0, 0, 4096
[9240990.133326] EXT4-fs (dm-21): orphan cleanup on readonly fs
[9240990.166215] EXT4-fs (dm-21): 6 orphan inodes deleted
[9240990.423904] EXT4-fs (dm-21): recovery complete
[9240990.703900] EXT4-fs (dm-21): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,data_err=abort,delalloc,nopriv,nodiscard,noacl
[9240991.394496] ext4_init_reserve_inode_table0: dm-21, 24576
[9240991.399970] ext4_init_reserve_inode_table2: dm-21, 24576, 0, 0, 4096
[9240991.408886] EXT4-fs (dm-21): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,data_err=abort,delalloc,nopriv,nodiscard,acl
[9241129.033140] EXT4-fs (sde1): error count since last fsck: 1
[9241129.038787] EXT4-fs (sde1): initial error at time 1645682288: ext4_orphan_get:1179
[9241129.046523] EXT4-fs (sde1): last error at time 1645682288: ext4_orphan_get:1179

At first sight this looks concerning. But a) this is a very recent drive and I don't see any reason why it should have a corrupt FS (no unclean unmount, energy outage or anything) and b) these orphan inode recovery messages keep showing up every now and then on QNAP's HDD partitions (again without unmount or outage background):

[9240990.133326] EXT4-fs (dm-21): orphan cleanup on readonly fs
[9240990.166215] EXT4-fs (dm-21): 6 orphan inodes deleted
[9240990.423904] EXT4-fs (dm-21): recovery complete

Is this something to be concerned of or it is just questionable ext logging? Or maybe the USB adapter?
And actually, I deem to remember that QNAP formated it ext3 so I'm a bit confused seeing ext4 messages.

thx
tcn

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,835

Re: ext4 orphan inodes - problem or false positive?

https://www.google.com/search?q=qnap+unclean+shutdown
Some service probably doesn't terminate and causes a forced shutdown/reboot. Seems common - but is not to be ignored either.
So check the system journals tail of the boot before this showed up.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

tcn

Member

Registered: 2011-09-30

Posts: 86

Re: ext4 orphan inodes - problem or false positive?

Thanks a lot. Looks like this file indicates an unclean unmount during shutdown:

# cat /etc/logs/.force_kill_in_shutdown.log