From: Theodore Ts'o <tytso@mit.edu>
To: EUNBONG SONG <eunb.song@samsung.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+
Date: Fri, 10 May 2013 15:27:47 -0400 [thread overview]
Message-ID: <20130510192747.GA11707@thunk.org> (raw)
In-Reply-To: <6719519.5821368147110937.JavaMail.weblogic@epml17>
Hmm, since you seem to be able to reproduce the problem reliably, any
chance you can try bisecting the problem? I've looked at the commits
that touch fs/jbd2 and nothing is jumping out at me.
Also, how many CPU's do you have your system, and what kind of storage
device were you using when you were running iozone (5400rpm HDD,
7200RPM HDD, RAID array, SSD, etc.)?
Thanks,
- Ted
next prev parent reply other threads:[~2013-05-10 19:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 0:51 Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ EUNBONG SONG
2013-05-10 17:27 ` Tony Luck
2013-05-11 7:52 ` Dmitry Monakhov
2013-05-13 2:04 ` Tony Luck
2013-05-13 3:07 ` Theodore Ts'o
2013-05-13 5:06 ` Sidorov, Andrei
2013-05-13 8:43 ` Zheng Liu
2013-05-10 19:27 ` Theodore Ts'o [this message]
2013-05-10 20:38 ` David Daney
2013-05-11 8:13 ` Nasty memory corrution v3.9-12555-g2dbd3ca Dmitry Monakhov
2013-05-11 9:17 ` Dmitry Monakhov
2013-05-11 11:00 ` EXT4 regression caused 4eec7 Dmitry Monakhov
2013-05-11 23:05 ` Theodore Ts'o
2013-05-12 9:01 ` Dmitry Monakhov
2013-05-13 16:34 ` Eric Sandeen
2013-05-13 17:01 ` Jan Kara
2013-05-13 17:09 ` Eric Sandeen
2013-05-14 7:11 ` Dmitry Monakhov
2013-05-14 14:08 ` Eric Sandeen
2013-05-14 22:04 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2013-05-13 2:21 Re: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ EUNBONG SONG
2013-05-13 3:11 ` Tony Luck
2013-05-13 3:36 ` Theodore Ts'o
2013-05-13 5:18 ` Mike Galbraith
2013-05-13 6:14 ` Tony Luck
2013-05-09 7:59 EUNBONG SONG
2013-05-09 15:31 ` Theodore Ts'o
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=20130510192747.GA11707@thunk.org \
--to=tytso@mit.edu \
--cc=eunb.song@samsung.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).