From: Luca Berra <bluca@comedia.it>
To: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Re: what superblock to use
Date: Mon, 20 Apr 2009 23:24:54 +0200 [thread overview]
Message-ID: <20090420212454.GC5550@maude.comedia.it> (raw)
In-Reply-To: <20090420193914009.EBTN9976@cdptpa-omta03.mail.rr.com>
On Mon, Apr 20, 2009 at 02:39:05PM -0500, Leslie Rhorer wrote:
>
>> >what's the current recommended superblock to use for a newly created
>> >raid5-6 array with 6 pieces of 1tb disk? by default mdamd use 0.90. is
>> >it worth to change it to any 1.x format?
>> 0.9 has some limitations that 1.x do not have, none apply in your case
>> max_components = 28
>> max_size of component=2TB
>
>Oops! I did not realize this when I built my array. I'm going to need to
>grow the array to 3T components after the 3T drives are released. Can the
>superblock be changed on an existing array, or does it have to be rebuilt
>from scratch? If the latter, I'm glad I learned this now, because I may
>have to rebuild the array, anyway, to try to alleviate the halt issue I am
>experiencing.
afaik it cannot be changed after creation
if you have free space you could play tricks reducing the fs, recreating
the array with the exact same parameters except metadata and
--assume-clean (you are limited to using 1.0 in this case)
anyway do a backup before trying this.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2009-04-20 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 13:39 what superblock to use Farkas Levente
2009-04-20 14:10 ` Andrew Burgess
2009-04-20 14:17 ` Luca Berra
2009-04-20 19:39 ` Leslie Rhorer
2009-04-20 21:24 ` Luca Berra [this message]
2009-04-20 14:17 ` Mario 'BitKoenig' Holbe
2009-04-21 17:31 ` H. Peter Anvin
2009-04-22 16:26 ` Leslie Rhorer
2009-04-21 14:20 ` Bill Davidsen
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=20090420212454.GC5550@maude.comedia.it \
--to=bluca@comedia.it \
--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).