From owner-freebsd-stable@FreeBSD.ORG Fri Nov 26 01:00:26 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2262216A4CE for ; Fri, 26 Nov 2004 01:00:26 +0000 (GMT) Received: from deskaheh.nysindy.org (host-69-48-73-242.roc.choiceone.net [69.48.73.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DA1143D5A for ; Fri, 26 Nov 2004 01:00:25 +0000 (GMT) (envelope-from ski@indymedia.org) Received: from 10.0.0.42 (unknown [10.0.0.254]) by deskaheh.nysindy.org (Postfix) with ESMTP id 0262141A2B for ; Thu, 25 Nov 2004 20:00:22 -0500 (EST) Received: from 10.0.0.120 (SquirrelMail authenticated user ski); by wuhjuhbuh.afraid.org with HTTP; Thu, 25 Nov 2004 20:01:01 -0500 (EST) Message-ID: <1969.10.0.0.120.1101430861.squirrel@10.0.0.120> In-Reply-To: <4802.10.0.0.26.1101417680.squirrel@10.0.0.26> References: <41A45A3F.5010008@anduin.net> <20041124171115.GP7232@darkness.comp.waw.pl> <6579E984-3E47-11D9-9576-000D9335BCEC@anduin.net> <20041125101405.GB7690@kevad.internal> <41A5B95F.3060605@withagen.nl> <4802.10.0.0.26.1101417680.squirrel@10.0.0.26> Date: Thu, 25 Nov 2004 20:01:01 -0500 (EST) From: "Brian Szymanski" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: gvinum raid 5 (was re: graid3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 01:00:26 -0000 > What's unusable about it? I've 4 250GB ATA drives, desiring capacity + > redundancy, but don't care about speed, much like you, and gvinum raid 5 > has suited me just fine this past few weeks. Eats a lot of system cpu when > there is heavy IO to the R5, but I've booted up with a drive unplugged and > it worked fine in degraded mode, so I'm content... Hmm... Maybe I got lucky/had an empty filesystem/hallucinated last time, but in any event when I try pulling the power on a drive now I get an error about a block not being found... Less than reassuring: drive 1: /dev/gvinum/big: CAN'T CHECK FILE SYSTEM /dev/gvinum/big: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY drive 2: /dev/gvinum/big: CANNOT READ BLK: 1401158656 /dev/gvinum/big: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY drive 3: /dev/gvinum/big: CANNOT READ BLK: 1401158656 /dev/gvinum/big: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY drive 4: Cannot find file system superblock /dev/gvinum/big: CANNOT READ BLK: 1401158656 /dev/gvinum/big: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY /dev/gvinum/big: CANNOT WRITE BLK: 12000 /dev/gvinum/big: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY --- THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/gvinum/big (/home) Automatic file system check failed; help! Pulling power on the RAID0/RAID1 arrays I have does what I expect it to do... Anyone have any idea what's going on here? Cheers, Brian Szymanski ski@indymedia.org