From mboxrd@z Thu Jan  1 00:00:00 1970
From: Goswin von Brederlow <goswin-v-b@web.de>
Subject: Re: RAID5 / 6 Growth
Date: Mon, 21 Dec 2009 13:33:25 +0100
Message-ID: <87pr68o6ay.fsf@frosties.localdomain>
References: <D6.C4.01550.4204D2B4@cdptpa-omtalb.mail.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-raid-owner@vger.kernel.org>
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")
Sender: linux-raid-owner@vger.kernel.org
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
List-Id: linux-raid.ids

"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