On Fri, Aug 05, 2016 at 10:02:28AM -0700, Darrick J. Wong wrote: > On Fri, Aug 05, 2016 at 12:35:44PM +0200, Johannes Stezenbach wrote: > > On Wed, Aug 03, 2016 at 05:50:26PM +0300, Török Edwin wrote: > > > I have just encountered a similar problem after I've recently upgraded to 4.7.0: > > > [Wed Aug 3 11:08:57 2016] EXT4-fs error (device dm-1): dx_probe:740: inode #13295: comm python: Directory index failed checksum > > > [Wed Aug 3 11:08:57 2016] Aborting journal on device dm-1-8. > > > [Wed Aug 3 11:08:57 2016] EXT4-fs (dm-1): Remounting filesystem read-only > > > [Wed Aug 3 11:08:57 2016] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal > > > > It just happened again to me, this time hitting /usr/sbin/ > > on root fs. Meanwhile I ran memtest86 7.0 for two nights, > > it didn't find anything. I'm using hibernate regularly > > and I think so this only happened after a few hibernate/resume > > cycles, but no idea if that means anything. > > Now I'm back at 4.4.16 to see if it reproduces. > > When you're back on 4.7, can you apply this patch[1] to see if it fixes > the problem? I speculate that the new parallel dir lookup code enables > multiple threads to be verifying the same directory block buffer at the > same time. > > [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ext4/inode.c?id=b47820edd1634dc1208f9212b7ecfb4230610a23 I added the patch, rebuilt and rebooted. It will take some time before I'll report back since the issue is so hard to reproduce. Thanks, Johannes -- 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
