From: Gilbert Kowarzyk <kowarzyk@grm.polymtl.ca>
To: NeilBrown <neilb@suse.de>
Cc: Michal Soltys <soltys@ziu.info>, linux-raid@vger.kernel.org
Subject: Re: Renaming MD devices (metadata=1.1)
Date: Wed, 11 Jan 2012 11:01:33 -0500 [thread overview]
Message-ID: <4F0DB25D.3030805@grm.polymtl.ca> (raw)
In-Reply-To: <20120111180347.0d177edf@notabene.brown>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
>> Why do we have these choices, and when should each be used?
>
> 1.0 (at the end) is best for RAID1 when booting from the device as
> the boot-load just doesn't see the RAID at all.
>
> 1.1 (at the start) is generally good because various different
> things have metadata at the start, so there is no chance of
> confusion about what is using that devices - each possible users
> will overwrite the metadata of the others. It is also easier to
> make the devices larger if you don't need to move the metadata.
>
> 1.2 (4K from the start) has most of the benefits for 1.1 but works
> for booting with newer boot loaders - they still want sector 0 for
> a boot sector but understand the md superblock.
I see. Makes also loads of sense.
I had two more quick questions:
1.- when would one want to turn off bitmaps? I turned them on, but I
haven't found why one may want them off (or for what they should be
turned off).
2.- if I ever have a mismatch_cnt different than zero, how would I go
about finding which drive has the correct info, which was the one that
got corrupted, and how to obtain the correct one?
In the past I've changed the "CHECK" to "REPAIR" in the configuration
script that checks the RAID arrays periodically
(/etc/sysconfig/raid-check), but from what I understood it's a bit of
luck which one the automatic script will choose out of the two drives
(assuming raid1). Should I let it be automatic (with "repair"), and if
not (if I have to check which one is correct manually), where could I
find information to read about how to do this (I am assuming the
answer may be long)?
Thanks!
Gilbert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: digital signature
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8NslwACgkQOYVp1RpLsmXUYQCfcAv/q33vjS2oqrxdey2wTEtn
yzwAnAhd7KT8Ye4JYO65MWm0dZZaa3d0
=yOmI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-11 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 6:12 Renaming MD devices (metadata=1.1) Gilbert Kowarzyk
2012-01-10 10:59 ` Michal Soltys
2012-01-11 6:07 ` Gilbert Kowarzyk
2012-01-11 6:20 ` NeilBrown
2012-01-11 6:39 ` Gilbert Kowarzyk
2012-01-11 7:03 ` NeilBrown
2012-01-11 16:01 ` Gilbert Kowarzyk [this message]
2012-01-11 23:04 ` NeilBrown
2012-01-12 0:08 ` Gilbert Kowarzyk
2012-01-10 12:49 ` Phil Turmel
2012-01-11 6:23 ` Renaming MD devices (metadata=1.1) [SOLVED] Gilbert Kowarzyk
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=4F0DB25D.3030805@grm.polymtl.ca \
--to=kowarzyk@grm.polymtl.ca \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=soltys@ziu.info \
/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.