From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 19:32:23 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D76371065679 for ; Sun, 29 Jun 2008 19:32:23 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 5958E8FC2B for ; Sun, 29 Jun 2008 19:32:22 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so772505fgb.35 for ; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=dRjCqaHZVSS0Mp6+xGOauynEjGzUnYQ5JkF+cgVN68I=; b=DnIhzz705ozaRzF/qrWqCYC99tK5a76N7uwNP9pNTSPDyhDKQzq3z0bcRj5x/BwId8 qYijXWYYsfT5dnO7j137R62m7wcbmm/I6VBZl07pfhXd9+OTvF3YTE+eni/VC91iKrU8 DlS7DC9OFSAe7PYZ+BYpCds2CUHmXy6PjBnos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SG+DrQIgolIX79464Zlu8nzhMB9UjoK/8T0ulCzVp6BJ3Ui+HTty0c/zbsprVkdRTB Ppa+tIdPx5ZBJHxD0TlFVgwzyQacILfRx4tC20FnVEgK8LM0GfVxmUM0rvmLU+oEWZpm o//NyHgj5XmDYeFTWiNFAupRc6nGLfU9Xjulo= Received: by 10.86.90.2 with SMTP id n2mr5101324fgb.51.1214767941615; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) Received: by 10.86.51.1 with HTTP; Sun, 29 Jun 2008 12:32:21 -0700 (PDT) Message-ID: <7d6fde3d0806291232o407b6391lcd223c2065ffa32c@mail.gmail.com> Date: Sun, 29 Jun 2008 12:32:21 -0700 From: "Garrett Cooper" To: "Steven Hartland" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7d6fde3d0806260649t6619521bv92b65c472ddb7e1@mail.gmail.com> <6.0.0.22.2.20080628132240.0255ba38@mail.computinginnovations.com> <7d6fde3d0806281410r781a6a77k98ffe237c10e3eee@mail.gmail.com> <7d6fde3d0806282011x472f8d27s955a8e1ab43a7341@mail.gmail.com> <48679898.3000905@clearchain.com> <43FD37E0-207A-4400-A95C-2301B5CD2B24@FreeBSD.ORG> Cc: Benjamin Close , current@freebsd.org, Rainer Duffner , =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: URGENT: Need help rebuilding iir RAID5 array with failed drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 19:32:24 -0000 On Sun, Jun 29, 2008 at 10:05 AM, Steven Hartland wrote: > > ----- Original Message ----- From: "S=F8ren Schmidt" >>> >>> 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