From: "NeilBrown" <neilb@suse.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID without superblock
Date: Mon, 20 Apr 2009 06:44:17 +1000 (EST) [thread overview]
Message-ID: <e96b335a0ba8595e2921d164f9b15ff7.squirrel@neil.brown.name> (raw)
In-Reply-To: <20090419114743.GA29195@lazy.lzy>
On Sun, April 19, 2009 9:47 pm, Piergiorgio Sartor wrote:
> Hi all,
>
> what is the proper way to assemble a two disk,
> RAID-1, without superblock.
> That is, created with "-B" instead of "-C".
Why would you want a RAID-1 without superblock. I generally
consider that a legacy configuration.
>
> I noticed that re-using "-B", will start an
> array sync/repair, but it is not clear to me
> which disk is source and which is destination.
As there is no superblock, md cannot tell if the array is "clean"
or not. It assumes the worst.
If you know for a fact that the two mirrors are consistent,
then tell mdadm with "--assume-clean".
>
> Using a bitmap file, seems to be safer option,
> but I'm not sure if this is just a workaround
> or it is the proper way.
A bitmap (which has to be in a separate file) can be use
to record the clean/dirty status. It provides some of the same
functionality as a superblock. But it is not a complete replacement.
To quote from the man page:
Because of this, the Build mode should only be used
together with a complete understanding of what you are doing.
NeilBrown
next prev parent reply other threads:[~2009-04-19 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 11:47 RAID without superblock Piergiorgio Sartor
2009-04-19 20:44 ` NeilBrown [this message]
2009-04-19 21:04 ` Piergiorgio Sartor
2009-04-19 21:57 ` Andrew Burgess
2009-04-20 18:10 ` Piergiorgio Sartor
2009-04-20 18:17 ` Christopher Chen
2009-04-19 23:33 ` John Robinson
2009-04-20 5:13 ` Tapani Tarvainen
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=e96b335a0ba8595e2921d164f9b15ff7.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
/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.