From: Ville Herva <vherva@niksula.hut.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: What are the recommended software RAID patch(es) for 2.2.20?
Date: Thu, 22 Nov 2001 21:54:24 +0200 [thread overview]
Message-ID: <20011122215424.C4809@niksula.cs.hut.fi> (raw)
In-Reply-To: <2173081930.1006455144@[195.224.237.69]> <20011122210503.B4809@niksula.cs.hut.fi>
In-Reply-To: <20011122210503.B4809@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Thu, Nov 22, 2001 at 09:05:03PM +0200
On Thu, Nov 22, 2001 at 09:05:03PM +0200, you [Ville Herva] claimed:
>
> cat /dev/hde | md5sum
> or
> cat /dev/hdg | md5sum
> (hdg and hde are not the same, but successive hde runs are the same as are
> hdg runs.)
>
> but
> cat /dev/md0 | md5sum
>
> is different every time. md0 consists of hde and hdg striped together.
> (Again, I'm not expecting it to be same as hde or hdg, but consistent over
> successive runs.) Successive hde and hdg runs are consistent even when run
> in parallel.
>
> Any ideas what could cause this? A short read or something else trivial?
>
> I'll try to go back to 2.2.18pre19 soon, and see if it happens there. Also,
> I'll try to see where the difference is. The first GB of md0 md5sums ok.
Ummh. I'm doing successive runs for /dev/md0 GB at a time, and it seems to
get corrupted in the middle:
#!/usr/bin/perl
for ($i = 0; $i < 75; $i++)
{
$block = 1024**2;
$count = 1024;
$| = 1;
print "At $i GB\n";
system "(dd if=/dev/md0 bs=$block count=$count skip=".($i*$count).
"| md5sum) 2>&1";
}
diff -c on (modified) output:
*** 5,11 ****
At 4 GB 131e2916f3155f7c6df63fe2257e0350 -
At 5 GB 502be9c039744eb761f89ada152a1745 -
At 6 GB 07012ffe77ad7d6565f2e9576f1cf91e -
! At 7 GB ffa5545ee518d3a7724831012d3e4c44 -
At 8 GB eec233bf66d33fc81bfa895b022c4b04 -
At 9 GB c62e78b9401f91199ce558242faf5da5 -
At 10 GB f41d004b63c2481245320c28b9366b08 -
--- 5,11 ----
At 4 GB 131e2916f3155f7c6df63fe2257e0350 -
At 5 GB 502be9c039744eb761f89ada152a1745 -
At 6 GB 07012ffe77ad7d6565f2e9576f1cf91e -
! At 7 GB 4bbbaeefe786c760e342342f6a85ad4e -
At 8 GB eec233bf66d33fc81bfa895b022c4b04 -
At 9 GB c62e78b9401f91199ce558242faf5da5 -
At 10 GB f41d004b63c2481245320c28b9366b08 -
(... still running)
I'm puzzled as to why this happens, since (as said) hde and hdg both md5sum
quite ok. Raid stuff, I gather, should be fairly solid, no?
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-11-22 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 18:52 Alex Bligh - linux-kernel
2001-11-22 19:05 ` Ville Herva
2001-11-22 19:54 ` Ville Herva [this message]
2001-11-23 12:35 ` HPT370 on 2.2.20+ide-patch Ville Herva
2001-11-23 14:39 ` HPT370 on 2.2.20+ide-patch - or is it RAID? Ville Herva
2001-11-23 21:32 ` Ville Herva
2001-11-24 6:52 ` HPT370 on 2.2.20+ide-patch - tried 2.4.15 and it fails, too Ville Herva
2001-11-24 7:17 ` Ville Herva
2001-11-25 14:06 ` HPT370 + IBM-DPTA-373420 corrupt data on 2.2 _and_ 2.4 Ville Herva
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=20011122215424.C4809@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--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
all inboxes | Powered by JetHome®