All of lore.kernel.org
 help / color / mirror / Atom feed
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 (more questions)
Date: Sun, 14 Jun 2009 01:10:00 -0600	[thread overview]
Message-ID: <200906140710.n5E7A5o7074412@cjb.net> (raw)
In-Reply-To: <200906132027.n5DKRquL067127@cjb.net>

So here I was thinking everything was fine.  My six disks were working
for hours and the other two disks were loaded as spares and the first
one was rebuilding, up to 30% with an ETA of 5 hours.  I left the house
for a few hours and when I came back, the same disk with read errors
before had spontaneously disconnected and reconnected three times (I
saw in dmesg).  It probably got around 80% of the way through the six
hour rebuild.

The problem is that when the /dev/sdc disk reconnected itself after,
it was marked as a "Spare", and now I can't use the same command any
longer:

# mdadm --assemble /dev/md13 --verbose --force /dev/sd{a,b,c,d,e,f}1

This time it doesn't work, as it says 5 disks and 1 spare isn't enough
to start the array.  I also tried --re-add, but it already thinks it
is disk 9 out of 8, a Spare.

How can I safely put this disk back into its proper place so I can
again try to rebuild disks 7 and 8?  I'm assuming I probably need to
use mdadm --create, but I'm not sure, and don't want to get it wrong
and have it overwrite this needed disk.

 - S.A.






  reply	other threads:[~2009-06-14  7:10 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     ` RAID-6 mdadm disks out of sync issue (five questions) linux-raid.vger.kernel.org
2009-06-11 23:33       ` 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                   ` linux-raid.vger.kernel.org [this message]
2009-06-14  8:11                     ` RAID-6 mdadm disks out of sync issue (more questions) 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=200906140710.n5E7A5o7074412@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 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.