From: Neil Brown <neilb@suse.de>
To: Jon@eHardcastle.com
Cc: jonathan.hardcastle@gmail.com,
Leslie Rhorer <lrhorer@satx.rr.com>,
Phil Turmel <philip@turmel.org>,
linux-raid@vger.kernel.org
Subject: Re: argh!
Date: Sun, 31 Oct 2010 17:44:40 -0400 [thread overview]
Message-ID: <20101031174440.586709a7@notabene> (raw)
In-Reply-To: <AANLkTimL=Z5gh+cbadd5+k66AoNZ8xc9upMbfE_Yqxac@mail.gmail.com>
On Sun, 31 Oct 2010 21:18:52 +0000
Jon Hardcastle <jonathan.hardcastle@gmail.com> wrote:
> Hi,
>
> Thanks for your help. I use 0.90 as that is what there was when the
> machine was build ~3yrs ago.. the array has been grown and resized
> since then.
>
> Does anyone have a feature list for the superblocks? Why upgrade.....?
The "md" man page mentions a couple of differences:
- v1.x can handle more than 28 devices in an array
- v1.x can easily be moved between hosts with different endian-ness
- v1.x can put the metadata at the front of the array
I should probably add the other differences.
- with 0.90 there can be confusion about whether a superblock applies
to the whole device or to just the last partition (if it start on a
64K boundary). 1.x doesn't have that problem
- With 1.x a device recovery can be checkpointed and restarted.
- with 0.90, the maximum component for RAID1 or higher is 2TB (or maybe
4TB, not sure). With 1.x you can go much higher.
Those are the only ones I can think of at the moment.
It is rarely worth the effort to upgrade, but usually best to choose 1.2
for new arrays that you don't want to boot off. If you want to boot of the
array, then whatever works with your boot-loader is the best choice.
NeilBrown
next prev parent reply other threads:[~2010-10-31 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 11:56 argh! Jon Hardcastle
2010-10-30 15:45 ` argh! Phil Turmel
2010-10-30 21:10 ` argh! Leslie Rhorer
2010-10-30 21:52 ` argh! Jon Hardcastle
2010-10-30 21:54 ` argh! Jon Hardcastle
2010-10-30 22:01 ` argh! Jon Hardcastle
2010-10-31 0:07 ` argh! Leslie Rhorer
2010-10-31 18:52 ` argh! Jon Hardcastle
2010-10-31 19:43 ` argh! Neil Brown
2010-10-31 19:54 ` argh! Jon Hardcastle
2010-11-01 21:39 ` argh! Leslie Rhorer
2010-10-31 0:05 ` argh! Leslie Rhorer
2010-10-30 23:57 ` argh! Leslie Rhorer
2010-10-31 21:18 ` argh! Jon Hardcastle
2010-10-31 21:44 ` Neil Brown [this message]
2010-11-01 1:51 ` argh! John Robinson
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=20101031174440.586709a7@notabene \
--to=neilb@suse.de \
--cc=Jon@eHardcastle.com \
--cc=jonathan.hardcastle@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
--cc=philip@turmel.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).