From owner-freebsd-stable@FreeBSD.ORG Thu Nov 11 19:05:34 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 C2C6516A4CE; Thu, 11 Nov 2004 19:05:34 +0000 (GMT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C1543D5C; Thu, 11 Nov 2004 19:05:34 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-228.de.inter.net ([213.73.76.228] helo=current.best-eng.de) by smart.eusc.inter.net with esmtp (Exim 3.36 #4) id 1CSKGC-0003OS-00; Thu, 11 Nov 2004 20:05:33 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iABJ5WhU001968; Thu, 11 Nov 2004 20:05:32 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iABJ5VQn001967; Thu, 11 Nov 2004 20:05:31 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: secmgr Date: Thu, 11 Nov 2004 20:05:31 +0100 User-Agent: KMail/1.7 References: <02f201c4ba91$f9f95db0$33017f80@psique> <200411071042.03382.msch@snafu.de> <4192889E.8010506@jim-liesl.org> In-Reply-To: <4192889E.8010506@jim-liesl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411112005.31694.msch@snafu.de> cc: freebsd-stable@freebsd.org cc: Lukas Ertl Subject: Re: freebsd 5.3 have any problem with vinum ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 19:05:35 -0000 Hello, Am Mittwoch, 10. November 2004 22:31 schrieben Sie: > ok, your instructions worked like a charm. So i'm running my nice 4 > member SCSI gvinum raid5 array (with softupdates turned on), and it's > zipping along. Fine! :-) > Now I need to test just how robust this is. Ouhh... ;-) > camcontrol is too nice. I want to test a more real world failure. > I'm running dbench and just pull one of the drives. My expectation > is that I should see a minor pause, and then the array continue in > some slower, degraded mode. That was mine too... > What I get is a kernel trap 12 (boom!). > I reboot, and it will not mount the degraded set till I replace the > drive. > > I turned off softupdates, and had the same thing happen. Is this a > bogus test? Is it reasonable to expect that a scsi drive failure > should of been tolerated w/o crashing? No, of course not. I have more or less the same problems here. Once I came so far as to delete the crashed subdisk but when I tried to delete the (not existing anymore) vinumdrive, my kernel also crashed... Well, to be honest, I once tried to pull the plug on one of my disks with 'classic' vinum and I got a kernel panic as well. OK, this happened a few years ago and I never tried that again... I'm not sure if this is a problem of (g)vinum or if FreeBSD has other problems in this area. And we all have to consider that gvinum is in a relatively early development phase (IMHO) - it is basically working, that is, it's possible to continue an existing 'classic' vinum installation with gvinum but it's still not fully functional in all depth. But I think, there's all the potential to get there. I have the impression that Lukas is *very* interested in his baby and I have a good overall feeling so far. But he's the only one developing gvinum AFAIK... And - my primary interest is the LVM functionality of (g)vinum. IMHO if you *really* have valuable data to protect, you can afford a hardware RAID-controller (*and* a tape drive :-). Anything else is wrong economy. But the current disk layout possibilities with up to four slices and at max 28 BSD-partitions are far to inflexible for todays large disks. So from this point of view I'm already fairly happy with gvinum as it is today. Which doesn't mean that I'm not trying to help to get gvinum to the place and state where it deserves to be... :-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F