All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: RAID-6 mdadm disks out of sync issue (more questions)
Date: Tue, 16 Jun 2009 05:38:28 +0200	[thread overview]
Message-ID: <20090616033828.GA9370@maude.comedia.it> (raw)
In-Reply-To: <b95d48b03b2756869e786c0982e54f86.squirrel@neil.brown.name>

On Sun, Jun 14, 2009 at 06:11:44PM +1000, NeilBrown wrote:
>On Sun, June 14, 2009 5:10 pm, linux-raid.vger.kernel.org@atu.cjb.net wrote:
>> 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:
>
>This doesn't make a lot of sense.  It should not have been marked as
>a spare unless someone explicitly tried to "Add" it to the array.
>
>I've been thinking that I need to improve mdadm in this respect
>and make it harder to accidentally turn a failed drive into a spare.
>
>However you description of event suggests that this was automatic
>which is strange.

udev?

>Can I get the complete kernel logs from when the rebuild started to
>when you finally gave up?  It might help me understand.

-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  parent reply	other threads:[~2009-06-16  3:38 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                   ` 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 [this message]
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=20090616033828.GA9370@maude.comedia.it \
    --to=bluca@comedia.it \
    --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.