From: Jens Axboe <axboe@suse.de>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Re: Reproducable OOPS with MD RAID-5 on 2.6.0-test11
Date: Mon, 1 Dec 2003 15:11:44 +0100 [thread overview]
Message-ID: <20031201141144.GD12211@suse.de> (raw)
In-Reply-To: <3FCB4AFB.3090700@backtobasicsmgmt.com>
On Mon, Dec 01 2003, Kevin P. Fleming wrote:
> I've got a new system here with six SATA disks set up in a RAID-5 array
> (no partition tables, using the whole disks). I then used LVM2 tools to
> make the RAID array a physical volume, created a logical volume and
> formatted that volume with an XFS filesystem.
>
> Mounting the filesystem and copying over the 2.6 kernel source tree
> produces this OOPS (and is pretty reproducable):
>
> kernel BUG at fs/bio.c:177!
It's doing a put on an already freed bio, that's really bad.
> invalid operand: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c014db9a>] Not tainted
> EFLAGS: 00010246
> EIP is at bio_put+0x2c/0x36
> eax: 00000000 ebx: f6221080 ecx: c1182180 edx: edcbf780
> esi: c577b998 edi: 00000002 ebp: edcbf780 esp: f78ffeb0
> ds: 007b es: 007b ss: 0068
> Process md0_raid5 (pid: 65, threadinfo=f78fe000 task=f7924080)
> Stack: c71e2640 c021d88d edcbf780 00000000 00000001 c1182180 00000009
> 0001000
> edcbf780 00000000 00000000 00000000 c014e2fc edcbf780 00000000
> 00000000
> f23a0ff0 f23a0ff0 edcbf7c0 c02ca51d edcbf780 00000000 00000000
> 00000000
> Call Trace:
> [<c021d88d>] bio_end_io_pagebuf+0x9a/0x138
> [<c014e2fc>] bio_endio+0x59/0x7e
> [<c02ca51d>] clone_endio+0x82/0xb5
> [<c02c0dc3>] handle_stripe+0x8f2/0xec0
> [<c02c17d1>] raid5d+0x71/0x105
> [<c02c898c>] md_thread+0xde/0x15c
> [<c011984b>] default_wake_function+0x0/0x12
> [<c02c88ae>] md_thread+0x0/0x15c
> [<c0107049>] kernel_thread_helper+0x5/0xb
Odds are it's a raid5 bug.
> Hardware is a 2.6CGHz P4, 1G of RAM (4G highmem enabled), SMP kernel but
> no preemption. Kernel config is at:
Are you using ide or libata as the backing for the sata drives?
--
Jens Axboe
next prev parent reply other threads:[~2003-12-01 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:06 Reproducable OOPS with MD RAID-5 on 2.6.0-test11 Kevin P. Fleming
2003-12-01 14:11 ` Jens Axboe [this message]
2003-12-01 14:15 ` Kevin P. Fleming
2003-12-01 15:51 ` Jens Axboe
2003-12-02 4:02 ` Kevin P. Fleming
2003-12-02 4:15 ` Mike Fedyk
2003-12-02 13:11 ` Kevin P. Fleming
2003-12-02 8:27 ` Jens Axboe
2003-12-02 10:10 ` Nathan Scott
2003-12-02 13:15 ` Kevin P. Fleming
2003-12-03 3:32 ` Nathan Scott
2003-12-03 17:13 ` Linus Torvalds
2003-12-02 18:23 ` Linus Torvalds
2003-12-04 1:12 ` Simon Kirby
2003-12-04 1:23 ` Linus Torvalds
2003-12-04 4:31 ` Simon Kirby
2003-12-05 6:55 ` Theodore Ts'o
2003-12-01 23:06 ` Reproducable OOPS with MD RAID-5 on 2.6.0-test11 - with XFS Neil Brown
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=20031201141144.GD12211@suse.de \
--to=axboe@suse.de \
--cc=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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).