From: Theodore Ts'o <tytso@mit.edu>
To: Nathaniel W Filardo <nwf@cs.jhu.edu>
Cc: linux-ext4@vger.kernel.org, admins@acm.jhu.edu,
Sander Smeenk <ssmeenk@freshdot.net>
Subject: Re: ext4 metadata corruption bug?
Date: Wed, 30 Jul 2014 22:37:44 -0400 [thread overview]
Message-ID: <20140731023744.GA17375@thunk.org> (raw)
In-Reply-To: <20140506155159.GY5136@gradx.cs.jhu.edu>
Hi,
Are you folks still seeing ext4_mb_generate_buddy or
ext4_mb_release_inode_pa EXT4-fs errors?
I think I may have found a fix for this problem. Or at least, I've
found one of the causes. If we get a memory allocation failure from
ext4_mb_new_inode_pa(), it can cause these errors. Actually
triggering it is a bit tricky, but it looks like we saw it hit when a
task which was running under high memory pressure (because it was
running right against its cgroup memory limit) core dump.
Anyway, if you are still seeing these issues, this patch might help you out:
http://patchwork.ozlabs.org/patch/375106/
If it works out for you, please let me know.
Cheers,
- Ted
next prev parent reply other threads:[~2014-07-31 2:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140409223820.GU10985@gradx.cs.jhu.edu>
[not found] ` <CAGagf4eEzY4+3cfNWSEENTo1PKe40nq1Ne6ZzOLGm-O78W7RcA@mail.gmail.com>
2014-04-10 5:04 ` ext4 metadata corruption bug? Nathaniel W Filardo
2014-04-10 14:03 ` Theodore Ts'o
2014-04-10 16:33 ` Nathaniel W Filardo
2014-04-10 22:17 ` Theodore Ts'o
2014-04-20 16:32 ` Nathaniel W Filardo
2014-04-20 17:57 ` Theodore Ts'o
2014-04-23 7:23 ` Sander Smeenk
2014-04-23 14:36 ` Theodore Ts'o
2014-04-23 15:30 ` Nathaniel W Filardo
2014-04-23 18:05 ` Sander Smeenk
2014-04-29 15:22 ` Nathaniel W Filardo
2014-05-01 16:25 ` Nathaniel W Filardo
2014-05-06 15:42 ` Theodore Ts'o
2014-05-06 15:51 ` Nathaniel W Filardo
2014-07-31 2:37 ` Theodore Ts'o [this message]
2014-08-06 8:53 ` Sander Smeenk
2014-05-01 17:02 ` Sander Smeenk
2014-05-06 14:22 ` Sander Smeenk
2014-05-26 14:59 ` Sander Smeenk
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=20140731023744.GA17375@thunk.org \
--to=tytso@mit.edu \
--cc=admins@acm.jhu.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=nwf@cs.jhu.edu \
--cc=ssmeenk@freshdot.net \
/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;
as well as URLs for NNTP newsgroup(s).