mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: 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:05:03 +0200	[thread overview]
Message-ID: <20011122210503.B4809@niksula.cs.hut.fi> (raw)
In-Reply-To: <2173081930.1006455144@[195.224.237.69]>
In-Reply-To: <2173081930.1006455144@[195.224.237.69]>; from linux-kernel@alex.org.uk on Thu, Nov 22, 2001 at 06:52:24PM -0000

On Thu, Nov 22, 2001 at 06:52:24PM -0000, you [Alex Bligh - linux-kernel] claimed:
> What are the recommended software RAID patch(es) for 2.2.20.
> 
> I have applied, but not yet tested, raid-2.2.19-A1, which
> fails on one hunk in init.c which I think is unimportant
> (seemingly 2.2.20 has a full boot line to device translation
> table without conditionality of compilation).

I just applied raid-2.2.19-A1 on 2.2.20 and have it running.
I'm not 100% sure it works, though, since I get always the same md5sum from

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.

I'm having a lot of problem with this setup, and raid code is not my primary
suspect. My gut feeling is that you should be safe with raid-2.2.19-A1 on
top of 2.2.20 and my problem is elsewhere.
 
> Do I need to apply anything else? (-A2, -A3, -B1, -B2 or
> whatever)

I reckon not. -B3, -A1 etc are version codes Ingo likes to use.


-- v --

v@iki.fi

  reply	other threads:[~2001-11-22 19:05 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 [this message]
2001-11-22 19:54   ` Ville Herva
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=20011122210503.B4809@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=linux-kernel@alex.org.uk \
    --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®