From: David Daney <ddaney.cavm@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
EUNBONG SONG <eunb.song@samsung.com>,
"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 13:38:57 -0700 [thread overview]
Message-ID: <518D5AE1.7040905@gmail.com> (raw)
In-Reply-To: <20130510192747.GA11707@thunk.org>
On 05/10/2013 12:27 PM, Theodore Ts'o wrote:
> 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.)?
I too have seen this.
My system is:
12 CPU Octeon (MIPS64)
Root is ext3, mounted via ext4fs on a slow CompactFlash/PIO6
I saw the crash when simply booting a fairly bare-bones Debian distro,
although it is somewhat random:
.
.
ata3: PATA max PIO6 cmd 900000001d040000 ctl 900000001d05000d irq 63
.
.
ata3.00: CFA: CF 4GB, 20101001, max UDMA/133
ata3.00: 7847280 sectors, multi 0: LBA
ata3.00: configured for PIO6
.
.
scsi 2:0:0:0: Direct-Access ATA CF 4GB 2010 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 7847280 512-byte logical blocks: (4.01 GB/3.74 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2
sd 2:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext3 filesystem) readonly on device 8:2.
.
.
.
I have not been able to get it to fail a second time. So for me
bisecting might not work.
David Daney
>
> Thanks,
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2013-05-10 20:38 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
2013-05-10 20:38 ` David Daney [this message]
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=518D5AE1.7040905@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=eunb.song@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).