All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Confusion with setting up new RAID6 with mdadm
Date: Sun, 14 Nov 2010 20:50:36 +0100	[thread overview]
Message-ID: <20101114195036.GA23982@maude.comedia.it> (raw)
In-Reply-To: <4CE00206.4000301@geograph.co.za>

On Sun, Nov 14, 2010 at 05:36:38PM +0200, Zoltan Szecsei wrote:
> *If I have to reformat the drives and redo mdadm --create, other than mdadm 
> stop, how can I get rid of all the /dev/md* etc etc so that when I restart 
> this exercise, the original bad RAID does not interfere with this new 
> attempt?

mdadm -Ss
mdadm --zero-superblock on each partition
>
>
> *Partition alignment?
> Is this relevant for modern HDs (I'm using 5900rpm Seagate 2TB drives)
for modern hdds with 4k sectors it is
new fdisk and/or parted should already know how to align
in any case, since you want to use the whole space for raid, why create
partitions at all, md works nicely without

> *Chunk size:
> After reading MANY different opinions, I'm guessing staying at the default 
> chunk size is optimal? Anyone want to add to this argument?
i believe the default in newer mdadm is fine

>
> *After partitioning the 8 drives, is this the correct sequence?
> mdadm --create /dev/md0 --metadata=1.2 --auto=md --chunk=64 --level=raid6 
why you state the chunk size here, i tought you wanted to stay with the
defauklt
> --raid devices=8 /dev/sd[abcdefgh]1
> mdadm --detail --scan >> /etc/mdadm.conf
> mdadm --assemble /dev/md0 /dev/sd[abcdefg]1
it should be already assembled after create, and after you appended the
info to mdadm.conf you just need mdadm --assemble /dev/md0 or mdadm
--assemble --scan.

> *After this, do I mkfs ext4 first, or LVM first?
if you want to use lvm it would be lvm first, but... do you want to?
there is no point if the aim is allocating the whole space to a single
filesystem.

> *What stride and stripe values should I use?
new toolstack should already find the correct stripe/stride for you

one more note:
for such a big array i would suggest to create a bitmap, so in case of
an unclean shutdown you do not have to wait for 27 hours for it to
rebuild. an internal bitmap will do.

L.

-- 
Luca Berra -- bluca@comedia.it

  parent reply	other threads:[~2010-11-14 19:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 15:36 Confusion with setting up new RAID6 with mdadm Zoltan Szecsei
2010-11-14 16:48 ` Mikael Abrahamsson
2010-11-15 12:27   ` Zoltan Szecsei
2010-11-15 12:47     ` Michal Soltys
2010-11-15 13:23       ` Zoltan Szecsei
2010-11-14 19:50 ` Luca Berra [this message]
2010-11-15  6:52   ` Zoltan Szecsei
2010-11-15  7:41     ` Luca Berra
2010-11-15 11:06       ` Zoltan Szecsei
2011-07-22  1:08   ` Tanguy Herrmann
2011-07-22  5:17     ` Mikael Abrahamsson
2010-11-14 22:13 ` Neil Brown
2010-11-15  5:30   ` Roman Mamedov
2010-11-15  6:58   ` Zoltan Szecsei
2010-11-15  7:43     ` Mikael Abrahamsson
2010-11-15  9:18       ` Neil Brown
2010-11-15 18:01   ` Zoltan Szecsei
2010-11-15 19:53     ` Neil Brown
2010-11-16  6:48       ` Zoltan Szecsei

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=20101114195036.GA23982@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 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.