linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice LORRAIN <Fabrice.Lorrain@univ-mlv.fr>
To: linux-raid@vger.kernel.org
Cc: Fabrice.Lorrain@univ-mlv.fr
Subject: Re: mdadm drives me crazy
Date: Wed, 01 Dec 2004 13:53:26 +0100	[thread overview]
Message-ID: <41ADBEC6.8030701@univ-mlv.fr> (raw)
In-Reply-To: <41ADA964.3030606@univ-mlv.fr>

Fabrice LORRAIN wrote:
> Hi all,
> 
...
> $ sudo mdadm --create /dev/md0 --level=5 --raid-devices=6 /dev/loop[0-5]


$ sudo mdadm --create /dev/md0 --force --level=5 --raid-devices=6 
/dev/loop[0-5]

Seems to give what I expected (a raid5 pool with 6 devices, no spare).

 From mdadm man page :
"...When creating a RAID5 array, mdadm will automatically create a 
degraded array with an extra spare drive.  This is because building the 
spare into a  degraded  array  is in general faster than resyncing the 
parity on a non-degraded, but not clean, array.  This feature can be 
over-ridden with the -I --force option."

"-I" doesn't seems to be understood by mdadm. Leftover ?

I don't understand what the previous extract from the man page means. My 
understanding is that the default behaviour of mdadm is to create a 
raid5 pool in degraded mode aka with a missing drive ? Is this correct ?

after
$ sudo mdadm --create /dev/md0 --force --level=5 --raid-devices=6 
/dev/loop[0-5]

the state of the array is dirty. Why ?

$ sudo mdadm --stop /dev/md0 followed by
$ sudo mdadm --examine /dev/loop[0-5]

gives a clean state for each device but

$ sudo mdadm --assemble /dev/md0 /dev/loop[0-5] keeps the dirty state of 
the array.

Thanks,

	Fab

  reply	other threads:[~2004-12-01 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 11:22 mdadm drives me crazy Fabrice LORRAIN
2004-12-01 12:53 ` Fabrice LORRAIN [this message]
2004-12-01 21:38   ` Neil Brown
2004-12-01 17:28 ` Guy

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=41ADBEC6.8030701@univ-mlv.fr \
    --to=fabrice.lorrain@univ-mlv.fr \
    --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).