From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: "Török Edwin" <edwin@etorok.net>,
linux-kernel@vger.kernel.org, tytso@mit.edu,
linux-ext4@vger.kernel.org
Subject: Re: 4.7.0-rc7 ext4 error in dx_probe
Date: Fri, 5 Aug 2016 12:15:48 -0700 [thread overview]
Message-ID: <20160805191548.GD19960@birch.djwong.org> (raw)
In-Reply-To: <20160805181136.mcjnnvuo5m6kpxzb@sig21.net>
On Fri, Aug 05, 2016 at 08:11:36PM +0200, Johannes Stezenbach wrote:
> 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.
FWIW I could trigger it reliably by running a bunch of directory traversal
programs simultaneously on the same directory. I have a script that fires
up multiple mutts pointing to the Maildirs for the high traffic Linux lists.
--D
>
> Thanks,
> Johannes
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-08-05 19:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:57 Johannes Stezenbach
2016-07-18 13:38 ` Theodore Ts'o
2016-07-18 14:17 ` Johannes Stezenbach
2016-07-27 11:58 ` Johannes Stezenbach
2016-08-03 14:50 ` Török Edwin
2016-08-05 10:35 ` Johannes Stezenbach
2016-08-05 17:02 ` Darrick J. Wong
2016-08-05 18:11 ` Johannes Stezenbach
2016-08-05 19:15 ` Darrick J. Wong [this message]
2016-08-08 3:56 ` Theodore Ts'o
2016-08-08 6:28 ` Darrick J. Wong
2016-08-08 16:08 ` Theodore Ts'o
2016-08-08 16:55 ` Darrick J. Wong
2016-08-08 21:13 ` Török Edwin
2016-08-09 2:37 ` Darrick J. Wong
2016-08-09 7:12 ` Török Edwin
2016-08-17 14:27 ` Török Edwin
2016-08-17 23:28 ` Darrick J. Wong
2016-08-22 7:33 ` Török Edwin
2016-09-01 16:40 ` Darrick J. Wong
2016-08-17 20:02 ` Johannes Stezenbach
2016-08-18 7:44 ` Török Edwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160805191548.GD19960@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=edwin@etorok.net \
--cc=js@sig21.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®