https://bugzilla.kernel.org/show_bug.cgi?id=40822 Sebastien Koechlin <seb.kernel@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seb.kernel@xxxxxxxxxxxx --- Comment #4 from Sebastien Koechlin <seb.kernel@xxxxxxxxxxxx> --- Sorry, I did not see that I had an answer on bugzilla. I will monitor it from now. Here is the situation: - The problem came back every few month during this time. I run many fsck, it usually correct things, but maybe not this particular deleted inode problem (fsck bug?). - I updated on 2014-02-10 to kernel 3.13.2 and e2fsck.static to 1.42.9-3 (e2fsck-static_1.42.9-2_i386.deb), and the problem happened today. - About hardware error: this server is running continuously since this initial bug report without problem (no other filesystem corrupted, no segfaults, no kernel ooops...) - About Host: Debian Linux 32bits, kernel is 64bits, RAID1+LVM2, many-many hardlinks (an inode has 29542 links), filesystem resized (to grow it) may times. It's always between 85 and 95% full. I have in dmesg: [3654666.866636] EXT4-fs error (device dm-4): ext4_lookup:1437: inode #300243: comm rsync: deleted inode referenced: 2748375 [3654666.911302] Aborting journal on device dm-4-8. [3654666.970296] EXT4-fs (dm-4): Remounting filesystem read-only [3654667.104392] EXT4-fs error (device dm-4): ext4_lookup:1437: inode #300243: comm rsync: deleted inode referenced: 2748375 Previous was using kernel 3.12.6: [ 3226.048137] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: errors=remount-ro,user_xattr [ 3526.870020] EXT4-fs (dm-4): error count: 21 [ 3526.870108] EXT4-fs (dm-4): initial error at 1372893876: ext4_lookup:1428: inode 915940 [ 3526.870271] EXT4-fs (dm-4): last error at 1372930167: ext4_put_super:762: inode 1676891 e2fsck just recover the journal and with -f does not find anything wrong. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
