From: Mike Fedyk <mfedyk@matchmail.com>
To: linux raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: RAID 5 from 2.4.24 to 2.6.0
Date: Thu, 8 Jan 2004 17:28:36 -0800 [thread overview]
Message-ID: <20040109012836.GT1882@matchmail.com> (raw)
In-Reply-To: <20040108151447.GA15294@piper.madduck.net>
On Thu, Jan 08, 2004 at 04:14:47PM +0100, Martin F Krafft wrote:
> Due to stability problems with the RAID code in 2.4 (detaailed
> message forthcoming), I would like to try 2.6.0 on one of our
> servers. However, anticipating problems, I want to make sure that
> this change is not irreversible.
>
> Can I mount RAID 1 and 5 partitions in 2.6.0 and 2.4.24
> interchangeably?
Yes, you can.
Though since the 2.4 raid code is quite fragile in states not possible from
2.4 code, I found one problem a while back where 2.6-test would set the state
bits wrong. The problem was fixed though.
You can use 2.6 and 2.4 raid interchangably, but don't scrimp on persuing
the problem from a 2.4 perspective.
prev parent reply other threads:[~2004-01-09 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 15:14 RAID 5 from 2.4.24 to 2.6.0 Martin F Krafft
2004-01-09 1:28 ` Mike Fedyk [this message]
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=20040109012836.GT1882@matchmail.com \
--to=mfedyk@matchmail.com \
--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).