From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: Reliability of bitmapped resync
Date: Mon, 23 Feb 2009 20:40:19 +0100 [thread overview]
Message-ID: <20090223194019.GA3488@lazy.lzy> (raw)
Hi all,
I've a strange issue.
I've a PC with 2 HDs in RAID-10 f2 with bitmap.
There are actually 3 md devices, boot, swap and root.
It happens that one SATA cable is/was flaky, so sometimes,
at boot, /dev/sdb does not show up.
The RAID starts in degraded mode, tracking the writes
in the bitmap.
On the next reboot, /dev/sdb is again there, so it is
possible to re-add it.
The md device resyncs what is to be resynced, very
quickly, due to the bitmap.
Later, if I run a check, usually a lot of mismatches
show up.
After repair (or add) further checks return zero mismatches.
Without boot failure, no mismatches showed up after check.
On a different PC, with same setup, but good cables,
something similar happened.
I tried, just for testing, to fail-remove-writeSomething-reAdd
one HD, a then run a check.
This was also returned some (few) mismatches.
Now, this test I did not repeat, so I cannot say this was
always the case.
Nevertheless I'm a bit concerned.
Is this behaviour somehow expected?
Is there something special to take into account when
removing and re-adding a RAID component?
Thanks a lot in advance,
bye,
--
piergiorgio
next reply other threads:[~2009-02-23 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:40 Piergiorgio Sartor [this message]
2009-02-23 19:59 ` Reliability of bitmapped resync NeilBrown
2009-02-23 20:19 ` Piergiorgio Sartor
2009-02-23 21:31 ` NeilBrown
2009-02-23 21:40 ` Piergiorgio Sartor
2009-02-23 21:49 ` NeilBrown
2009-02-24 19:39 ` Piergiorgio Sartor
2009-02-25 2:39 ` Neil Brown
2009-02-25 18:51 ` Piergiorgio Sartor
2009-03-13 17:19 ` Bill Davidsen
2009-02-23 21:18 ` Eyal Lebedinsky
2009-02-23 21:36 ` Piergiorgio Sartor
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=20090223194019.GA3488@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--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).