linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Patrik Jonsson <patrik@ucolick.org>
Cc: Daniel Santos <daniel.dlds@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: problem killing raid 5
Date: Tue, 02 Oct 2007 00:35:32 +0400	[thread overview]
Message-ID: <47015A14.9020400@msgid.tls.msk.ru> (raw)
In-Reply-To: <47014368.4040204@ucolick.org>

Patrik Jonsson wrote:
> Michael Tokarev wrote:
[]
>> But in any case, md should not stall - be it during reconstruction
>> or not.  For this, I can't comment - to me it smells like a bug
>> somewhere (md layer? error handling in driver? something else?)
>> which should be found and fixed.  And for this, some more details
>> are needed I guess -- kernel version is a start.
> 
> Really? It's my understanding that if md finds an unreadable block
> during raid5 reconstruction, it has no option but to fail since the
> information can't be reconstructed. When this happened to me, I had to

Yes indeed, it should fail, but not stuck as Daniel reported.
Ie, it should either complete the work or fail, but not sleep
somewhere in between.

[]
> This is why it's important to run a weekly check so md can repair blocks
> *before* a drive fails.

*nod*.

/mjt

  reply	other threads:[~2007-10-01 20:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 11:04 problem killing raid 5 Daniel Santos
2007-10-01 18:20 ` Daniel Santos
2007-10-01 18:47   ` Michael Tokarev
2007-10-01 18:58     ` Patrik Jonsson
2007-10-01 20:35       ` Michael Tokarev [this message]
2007-10-01 21:11         ` Daniel Santos
2007-10-01 21:44           ` Justin Piszcz
2007-10-02  6:53             ` Daniel Santos

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=47015A14.9020400@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=daniel.dlds@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=patrik@ucolick.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).