From: Goswin von Brederlow <goswin-v-b@web.de>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 / 6 Growth
Date: Mon, 21 Dec 2009 13:33:25 +0100 [thread overview]
Message-ID: <87pr68o6ay.fsf@frosties.localdomain> (raw)
In-Reply-To: <D6.C4.01550.4204D2B4@cdptpa-omtalb.mail.rr.com> (Leslie Rhorer's message of "Sat, 19 Dec 2009 15:05:37 -0600")
"Leslie Rhorer" <lrhorer@satx.rr.com> writes:
>> I understand what you're aiming at finding, unfortunately I can't
>> think of anything that would cause a corruption apart from bad cables
>> or bad sectors.
>
> Well, me, either, but the question at hand isn't so much, "What
> caused it?" as it is, "Is there something (above and beyond the resync which
> was already done) I can do to verify the health of the underlying array
> before proceeding?"
Run a check.
MfG
Goswin
next prev parent reply other threads:[~2009-12-21 12:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70ed7c3e0912191232k7deb3a3p40ddd6bc1bdfd3ae@mail.gmail.com>
2009-12-19 21:05 ` RAID5 / 6 Growth Leslie Rhorer
2009-12-21 12:33 ` Goswin von Brederlow [this message]
2009-12-16 5:40 Leslie Rhorer
2009-12-16 6:37 ` Majed B.
2009-12-16 8:06 ` Leslie Rhorer
2009-12-16 8:12 ` Michael Evans
2009-12-16 8:38 ` Leslie Rhorer
2009-12-16 11:21 ` Majed B.
2009-12-17 1:36 ` Leslie Rhorer
2009-12-19 1:13 ` Leslie Rhorer
2009-12-19 18:21 ` Leslie Rhorer
2009-12-19 18:36 ` Majed B.
2009-12-19 19:02 ` Leslie Rhorer
2009-12-19 19:55 ` Majed B.
2009-12-19 20:19 ` Leslie Rhorer
2009-12-19 23:39 ` John Robinson
2009-12-19 23:49 ` Leslie Rhorer
2009-12-19 23:59 ` Majed B.
2009-12-16 13:25 ` Goswin von Brederlow
2009-12-17 1:51 ` Leslie Rhorer
2009-12-17 9:27 ` John Robinson
2009-12-18 1:33 ` Leslie Rhorer
2009-12-19 1:11 ` Leslie Rhorer
2009-12-18 12:27 ` Goswin von Brederlow
2009-12-17 17:53 ` Bill Davidsen
2009-12-18 1:46 ` Leslie Rhorer
2009-12-19 1:12 ` Leslie Rhorer
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=87pr68o6ay.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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