Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jun 2008 12:32:21 -0700
From:      "Garrett Cooper" <yanefbsd@gmail.com>
To:        "Steven Hartland" <killing@multiplay.co.uk>
Cc:        Benjamin Close <Benjamin.Close@clearchain.com>, current@freebsd.org, Rainer Duffner <rainer@ultra-secure.de>, =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@freebsd.org>
Subject:   Re: URGENT: Need help rebuilding iir RAID5 array with failed drive
Message-ID:  <7d6fde3d0806291232o407b6391lcd223c2065ffa32c@mail.gmail.com>
In-Reply-To: <B14F86C7175B42628E15687A263C8DA1@multiplay.co.uk>
References:  <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <D0A03968-B9F2-4EF8-B754-D0EFA90A9C1E@FreeBSD.ORG> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <F8F21D91-0BF9-4525-A397-D2632821C7E5@ultra-secure.de> <48679898.3000905@clearchain.com> <FAEE486EB48B440A866156003FBA41C9@multiplay.co.uk> <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> <B14F86C7175B42628E15687A263C8DA1@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 29, 2008 at 10:05 AM, Steven Hartland
<killing@multiplay.co.uk> wrote:
>
> ----- Original Message ----- From: "S=F8ren Schmidt" <sos@FreeBSD.ORG>
>>>
>>> Although it is more visible, personally I would prefer it to just fail
>>> instead of proceeding. RAID5 is not RAID5 without parity so why even
>>> allow it to continue and hence risk such an unrecoverable situation?
>>
>> Well, this has been rehashed many times before, it has been disabled,  p=
ut
>> a warning in the boot log, warning in the docs, all 3 was the  favorite =
at
>> the time it was done.
>>
>> I'm all ears for what the decision might be this time, just get  consens=
us
>> and I'll flip the right switch.
>
> As a small expansion to this, a good compromise might be to disable it
> unless a sysctl flag is explicitly set. Similar to how the sysctl
> kern.geom.debugflags=3D16 works? Then for those that know the implication=
s
> they can still have the functionality but prevents someone stumbling
> into a nasty situation without being aware of the issues.
>
>   Regards
>   Steve

That wouldn't have helped me in this situation because I didn't set
anything up via geom, because I was blissfully unaware and didn't ask
how anyone to setup a RAID config properly before now.
That idea probably wouldn't be a bad one though...
-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0806291232o407b6391lcd223c2065ffa32c>