From: Phil Turmel <philip@turmel.org>
To: NeilBrown <neilb@suse.de>
Cc: Stephen Muskiewicz <stephen_muskiewicz@uml.edu>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Need help recovering RAID5 array
Date: Tue, 09 Aug 2011 07:38:51 -0400 [thread overview]
Message-ID: <4E411C4B.1080200@turmel.org> (raw)
In-Reply-To: <20110809125549.00c56f57@notabene.brown>
On 08/08/2011 10:55 PM, NeilBrown wrote:
> On Mon, 8 Aug 2011 22:29:10 -0400 Stephen Muskiewicz <stephen_muskiewicz@uml.edu> wrote:
>> This does lead to a question: Do you recommend (and is it safe on CentOS
>> 5.5?) for me to use the updated (3.2.2 with your patch) version of mdadm
>> going forward in place of the CentOS version (2.6.9)?
>
> I wouldn't kept that patch. It was a little hack to get your array working
> again. I wouldn't recommend using it without expert advice...
>
> Other than that ... 3.2.2 certainly fixes bug and adds features over 2.6.9,
> but maybe it adds some bugs too... I would say that it is safe, but probably
> not really necessary.
> i.e. up to you :-)
Let me add a reason to stick with 2.6.9: it has different defaults for
metadata reserved space. If all hell breaks loose, and you find you need to
do "mdadm --create --assume-clean" or some variant as part of your recovery
efforts, you'll need the older version to get an identical layout.
Phil
next prev parent reply other threads:[~2011-08-09 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 15:27 Need help recovering RAID5 array Stephen Muskiewicz
2011-08-06 1:29 ` NeilBrown
2011-08-08 17:41 ` Muskiewicz, Stephen C
2011-08-08 23:12 ` NeilBrown
2011-08-09 2:29 ` Stephen Muskiewicz
2011-08-09 2:55 ` NeilBrown
2011-08-09 11:38 ` Phil Turmel [this message]
2011-08-09 14:47 ` Muskiewicz, Stephen C
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=4E411C4B.1080200@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stephen_muskiewicz@uml.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.