From: NeilBrown <neilb@suse.de>
To: LuVar <luvar@plaintext.sk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: unsynchronized raid10 with different events count
Date: Thu, 5 Feb 2015 15:52:52 +1100 [thread overview]
Message-ID: <20150205155252.053096e9@notabene.brown> (raw)
In-Reply-To: <850189010.36671422720846038.JavaMail.root@shiva>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Sat, 31 Jan 2015 17:14:06 +0100 (GMT+01:00) LuVar <luvar@plaintext.sk>
wrote:
> Hi,
> finally,
> I have run --re-add thing. It seems that it is what I wanted. My array is now OK.
>
> So only one question remains. Is there any possibility to make improvements and make array autoassemble if there are clear that in raid10, there is consistent highest events count for at least one drive for raid1 subparts? I have layout=n3 for situations when one drive fails, to be able to correctly recover from others two same copies and to know that given data are probably ok if they are same.
It appears from the mdstat you posted:
Personalities : [raid10]
md3 : active raid10 sdj[9] sdl[13] sdm[6] sdi[3] sdb[10]
937709952 blocks super 1.2 128K chunks 3 near-copies [9/5] [U_UU__UU_]
bitmap: 4/7 pages [16KB], 65536KB chunk
unused devices: <none>
That it *did* autoassemble and provide you with a working array. It just
didn't include all the devices - because some of them looked old and mdadm
couldn't be sure they were reliable.
You did the correct thing to --re-add them. That is how you tell mdadm
"these devices are reliable, even though someone went wrong before and they
didn't get updated with the latest event count".
So it appears to me that everything is working correctly.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-02-05 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 13:52 unsynchronized raid10 with different events count LuVar
2015-01-31 14:33 ` LuVar
2015-01-31 16:14 ` LuVar
2015-02-05 4:52 ` NeilBrown [this message]
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=20150205155252.053096e9@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=luvar@plaintext.sk \
/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).