From: Tupshin Harper <tupshin@tupshin.com>
To: Christophe Saout <christophe@saout.de>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: data corruption using raid0+lvm2+jfs with 2.6.0-test3
Date: Tue, 12 Aug 2003 14:10:35 -0700 [thread overview]
Message-ID: <3F3957CB.70006@tupshin.com> (raw)
In-Reply-To: <1060722538.8344.11.camel@chtephan.cs.pocnet.net>
Christophe Saout wrote:
>Am Di, 2003-08-12 um 22.45 schrieb Tupshin Harper:
>
>
>
>>I have an LVM2 setup with four lvm groups. One of those groups sits on
>>top of a two disk raid 0 array. When writing to JFS partitions on that
>>lvm group, I get frequent, reproducible data corruption. This same setup
>>works fine with 2.4.22-pre kernels. The JFS may or may not be relevant,
>>since I haven't had a chance to use other filesystems as a control.
>>There are a number of instances of the following message associated with
>>the data corruption:
>>
>>raid0_make_request bug: can't convert block across chunks or bigger than
>>8k 12436792 8
>>
>>The 12436792 varies widely, the rest is always the same. The error is
>>coming from drivers/md/raid0.c.
>>
>>
>
>Why don't you try using an LVM2 stripe? That's the same as raid0 does.
>And I'm sure it doesn't suffer from such problems because it's handling
>bios in a very generic and flexible manner.
>
Yes, I'm already converting to such a setup as I type this. I thought
that a data corruption issue was worth mentioning, however. ;-)
-Tupshin
next prev parent reply other threads:[~2003-08-12 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 20:45 data corruption using raid0+lvm2+jfs with 2.6.0-test3 Tupshin Harper
2003-08-12 21:08 ` Christophe Saout
2003-08-12 21:10 ` Tupshin Harper [this message]
2003-08-12 21:28 ` Andrew Morton
2003-08-12 23:05 ` Neil Brown
2003-08-13 7:25 ` Joe Thornber
2003-08-15 21:27 ` Mike Fedyk
2003-08-16 8:00 ` Neil Brown
2003-08-16 14:18 ` Lars Marowsky-Bree
2003-08-16 23:52 ` Mike Fedyk
2003-08-17 0:12 ` Neil Brown
2003-08-17 17:50 ` Mike Fedyk
2003-08-17 23:14 ` Neil Brown
2003-08-18 0:28 ` Mike Fedyk
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=3F3957CB.70006@tupshin.com \
--to=tupshin@tupshin.com \
--cc=christophe@saout.de \
--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