From: <linux-raid.vger.kernel.org@atu.cjb.net>
To: linux-raid@vger.kernel.org
Subject: Re: RAID-6 mdadm disks out of sync issue (five questions)
Date: Thu, 11 Jun 2009 12:43:42 -0600 [thread overview]
Message-ID: <200906111843.n5BIhlcN024789@cjb.net> (raw)
In-Reply-To: <ed308b763e18e168a98f977857663bed.squirrel@neil.brown.name>
NeilBrown <neilb@suse.de> wrote :
> Once you are sure you have the 6 drives with the highest
> event counts working, assemble them with
>
> mdadm --assemble /dev/md13 --force /dev/sd?1
I had a few questions before I went ahead with the
reassembly:
1) Does it matter which order the disks are listed in when
reassembling the array (e.g. /dev/sda1 /dev/sdh1 ...)?
2) Is there any risk to the data stored on the disks by
merely reassembling the six working disks with the above
command?
3) Does /sys/module/md_mod/parameters/start_ro being
set to 1 prevent the array from syncing/rebuilding/etc.,
or does it only prevent new user data being written to
the array? If it only prevents user data being written
to the /dev/md*, is there some way to also prevent mdadm
from doing syncing/rebuilding/etc. so I can be sure the
data is not at risk of further damage while testing?
4) Having checked what the "Events" refers to (I thought it
was write-syncing operations before), should I be worried
at the Event count being above 1,000,000? I have rebuilt
two failed disks and the distro performed a few data
integrity checks on all the disks. The array is about
nine to ten months old.
5) Any idea why "shutdown -h now" would cause three of
the six working disks to gain 4 events each (happened with
the filesystem unmounted from /dev/md13)?
- S.A.
next prev parent reply other threads:[~2009-06-11 18:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1752989AbZFJCy5/20090610025457Z+40@vger.kernel.org>
2009-06-10 8:52 ` RAID-6 mdadm disks out of sync issue (long e-mail) linux-raid.vger.kernel.org
2009-06-10 10:55 ` NeilBrown
2009-06-11 18:43 ` linux-raid.vger.kernel.org [this message]
2009-06-11 23:33 ` RAID-6 mdadm disks out of sync issue (five questions) Michael Tokarev
2009-06-12 1:26 ` Neil Brown
2009-06-13 9:18 ` RAID-6 mdadm disks out of sync issue (no success) linux-raid.vger.kernel.org
2009-06-13 9:24 ` linux-raid.vger.kernel.org
2009-06-13 9:58 ` NeilBrown
2009-06-13 18:02 ` linux-raid.vger.kernel.org
2009-06-13 20:27 ` RAID-6 mdadm disks out of sync issue (success!) linux-raid.vger.kernel.org
2009-06-14 7:10 ` RAID-6 mdadm disks out of sync issue (more questions) linux-raid.vger.kernel.org
2009-06-14 8:11 ` NeilBrown
2009-06-14 21:01 ` linux-raid.vger.kernel.org
2009-06-15 15:48 ` Bill Davidsen
2009-06-16 6:00 ` Neil Brown
2009-06-16 8:13 ` linux-raid.vger.kernel.org
2009-06-16 3:38 ` Luca Berra
2009-06-16 5:00 ` linux-raid.vger.kernel.org
2009-06-10 8:58 ` RAID-6 mdadm disks out of sync issue (long e-mail) linux-raid.vger.kernel.org
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=200906111843.n5BIhlcN024789@cjb.net \
--to=linux-raid.vger.kernel.org@atu.cjb.net \
--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).