From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: Accidental grow before add
Date: Sun, 26 Sep 2010 11:38:18 +0100 [thread overview]
Message-ID: <20100926103818.GA5719@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <AANLkTikOr3LdZ_uy5Vnj=wu0k7Ag8A+LXRYwxf69YNOv@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
On Sun Sep 26, 2010 at 06:18:09AM -0400, Mike Hartman wrote:
> > You need to start looking in dmesg / other logs to see what has happened and
> > why things have failed. Without that information it's impossible to tell
> > what's going on.
> >
> I've uploaded the dmesg output starting with the reshape to
> www.hartmanipulation.com/raid/dmesg_6.txt. It looks like /dev/sdd is
> having some kind of intermittent read issues (which wasn't happening
> before the reshape started) but I still don't understand why it
> wouldn't be marked as failed in the md2 section of mdstat, since md0
> is accessing it via md2.
>
I think this is because it's a RAID0 array. It can't fail the device
without (irrecoverably) failing the array, so it's left to the normal
block device error reporting/handling process.
> At any rate, that doesn't help me with my most immediate issue: does a
> drive failing during a reshape corrupt the array? Or am I safe to
> resume the reshape? Is there any way to restore my safety net a bit
> before resuming the reshape, or will I just have to hope nothing else
> goes wrong between now and the time the new hot spare is finally
> incorporated?
>
Failure of a device during the reshape certainly shouldn't corrupt the
array (I don't see how it would anyway, unless there's a screw-up in the
code). I don't think there's any way to "restore your safety net"
though (short of imaging all the drives as backups), but it's probably
worth while doing a read test of all member devices before you continue.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-26 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 7:27 Accidental grow before add Mike Hartman
2010-09-26 9:39 ` Mike Hartman
2010-09-26 9:54 ` Mike Hartman
2010-09-26 9:59 ` Mikael Abrahamsson
2010-09-26 10:18 ` Mike Hartman
2010-09-26 10:38 ` Robin Hill [this message]
2010-09-26 19:34 ` Mike Hartman
2010-09-26 21:22 ` Robin Hill
2010-09-27 8:11 ` Jon Hardcastle
2010-09-27 9:05 ` Mike Hartman
2010-09-28 15:14 ` Nagilum
2010-10-05 5:18 ` Neil Brown
2010-09-30 16:13 ` Mike Hartman
2010-10-05 6:24 ` Neil Brown
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=20100926103818.GA5719@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--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).