From: Andrey Borzenkov <arvidjaar@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Handling of stale array members in Linux MD
Date: Sat, 16 Mar 2013 12:04:51 +0400 [thread overview]
Message-ID: <20130316120451.4cd714c3@opensuse.site> (raw)
I'm looking at adding validation of array members to grub2 array
assembly code and have some questions.
1. As far as I understand, two devices are compared basing on single 64
bit event counter. I do not see any counter wrap around check. Is it
something that can not ever happen?
2. When array is declared ready for use? I.e. consider RAID10 with 4
members where each mirror pair lost one member. E.g. due to
connectivity failure. After some time system is rebooted and second
pair is lost, but the first one is now available. So we get valid array
(both stale members have the same event counter). Will array be
assembled at this point? What happens if other two device appear later?
Will the be kicked off array?
Thank you in advance
-andrey
reply other threads:[~2013-03-16 8:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130316120451.4cd714c3@opensuse.site \
--to=arvidjaar@gmail.com \
--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).