https://bugzilla.kernel.org/show_bug.cgi?id=89621 --- Comment #7 from Theodore Tso <tytso@xxxxxxx> --- OK, so vis-a-vis case #1, it looks like the fsck didn't take. Dec 3 11:04:26 cedric kernel: [ 1.440438] EXT4-fs (dm-0): mounting ext3 file system using the ext4 subsystem Dec 3 11:04:26 cedric kernel: [ 1.468114] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) Dec 3 11:04:26 cedric kernel: [ 6.139705] EXT4-fs (dm-0): re-mounted. Opts: (null) Dec 3 11:04:26 cedric kernel: [ 6.311768] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro Dec 3 11:09:11 cedric kernel: [ 302.048065] EXT4-fs (dm-0): error count since last fsck: 3 Dec 3 11:09:11 cedric kernel: [ 302.048102] EXT4-fs (dm-0): initial error at time 1417556618: ext4_mb_release_inode_pa:3773 Dec 3 11:09:11 cedric kernel: [ 302.048105] EXT4-fs (dm-0): last error at time 1417596801: ext4_remount:4853 I'm not exactly sure what time zone your system messages are in, but e2fsck 1.42.5 (I assume you're using e2fsprogs from debian stable?) will clear the error stats, and time 1417596801 is: % TZ=GMT date -d @1417596801 Wed Dec 3 08:53:21 GMT 2014 Either that, or maybe the raid system is acting up and writes aren't going to both halves, or something weird like that? Can you do me a favor and configure a handful of VM's that ***don't*** use MD RAID, just so we can rule out funny business on that score? -- 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
