From: Tejun Heo <htejun@gmail.com>
To: linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>
Subject: Re: Possible data corruption sata_sil24?
Date: Fri, 13 Jul 2007 16:34:06 +0900 [thread overview]
Message-ID: <46972AEE.2040805@gmail.com> (raw)
In-Reply-To: <20070713014252.GA17811@jabberwocky.com>
Hello,
David Shaw wrote:
>>> Starting with two 500GB SATA drives (interface card uses a Silicon
>>> 3124 chipset), /dev/sdd and /dev/sde. I partitioned each into two
>>> 250GB chunks (250*1000*1000*1000, not 250*1024*1024*1024), and set up
>>> two RAID 1 sets such that /dev/md0 is /dev/sdd1+/dev/sde1 and /dev/md2
>>> is /dev/sdd2+/dev/sde2. I then created a volume group ("storage") on
>>> top of /dev/md0 and /dev/md1. Finally, I allocated two logical
>>> volumes on top of that: "one" is -L300GB and "two" is -L100GB.
>> -ETOOMANYCOMPNONETS. If it's data corruption with sata_sil24, it's
>> highly likely that you're gonna be able to regenerate the problem
>> without using raw /dev/sdd and /dev/sde devices. Please try that.
Oops, sorry, s/without/with/
> It fails whether I use a raw /dev/sdd or partition it into one large
> /dev/sdd1, or partition into multiple partitions. sata_sil24 seems to
> work by itself, as does dm, but as soon as I mix sata_sil24+dm, I get
> corruption.
Hmmmm.... Can you reproduce the corruption by accessing both devices
simultaneously without using dm? Considering ich5 does fine, it looks
like hardware and/or driver problem and I really wanna rule out dm.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-07-13 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 1:24 Possible data corruption sata_sil24? David Shaw
2007-07-10 15:28 ` Tejun Heo
2007-07-13 1:42 ` David Shaw
2007-07-13 7:34 ` Tejun Heo [this message]
2007-07-13 11:59 ` David Shaw
2007-07-18 8:53 ` Tejun Heo
2007-07-18 12:31 ` David Shaw
2007-07-19 8:03 ` Tejun Heo
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=46972AEE.2040805@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@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).