From owner-freebsd-questions@FreeBSD.ORG Wed Mar 16 23:15:44 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D6A16A4CF for ; Wed, 16 Mar 2005 23:15:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F6E143D1D for ; Wed, 16 Mar 2005 23:15:42 +0000 (GMT) (envelope-from linicks@gmail.com) Received: by rproxy.gmail.com with SMTP id g11so297606rne for ; Wed, 16 Mar 2005 15:15:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=EIfBMLqAsy4gcHbbbEaVm2ik1C/vvboHEILcqE5zKO8b6tHhY5De7GEuHM0XVlqotGxobQVNHCQBSZklhEJEqY+XpdkC10pXhqMVhzSHBDKK1PVtMS7jVFH6f8zp2Aj9n8gzJcCjipnfx5YK+Kh9GPsyR3Sp7oyruVnzJ2Q2jDc= Received: by 10.39.1.24 with SMTP id d24mr982216rni; Wed, 16 Mar 2005 15:15:41 -0800 (PST) Received: by 10.38.165.35 with HTTP; Wed, 16 Mar 2005 15:15:41 -0800 (PST) Message-ID: Date: Wed, 16 Mar 2005 16:15:41 -0700 From: Nick Pavlica To: John Pettitt In-Reply-To: <4238A904.6040801@cloudview.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <42376647.4030008@netfence.it> <4238A904.6040801@cloudview.com> cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5.3+ Vinum or Gvinum X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nick Pavlica List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 23:15:44 -0000 John, That did the trick. I built a new kernel with the GEOM_STRIPE option and added an entry to my fstab to mount the volume(stripe) and everything worked like a charm. In the end this turned out to be much simpler than I had anticipated. I wish this information would have been available in the online documentation (Hand Book). I wouldn't have even known about gstripe, if it were not for the people on this list. I wounder how many undocumented gems are out there. Thanks Again! --Nick On Wed, 16 Mar 2005 13:45:40 -0800, John Pettitt wrote: > > > Nick Pavlica wrote: > Andrea, I have started testing with gstripe and have had good results to > this point. I'm still a little unclear about how to make my stripe > persistent after a reboot? My server consists of three drives. A 40GB drive > that has the operating system and two 200Gb drives that I'm using for the > raid 0 volume. I was also curious about a couple of other things. If you > made the stripe using something like > > gstripe label -v -s somenumber data /dev/mumble1 /dev/mumble2 > > then it will be persistent subject to gstripe being loaded in the kernel - > use gstripe load or build a kernel with "options GEOM_STRIPE " > > You see something like > > GEOM_STRIPE: Device data2 created (id=889964967). > GEOM_STRIPE: Disk da0 attached to data2. > GEOM_LABEL: Label for provider da1 is ufs/data. > GEOM_STRIPE: Disk da2 attached to data2. > GEOM_STRIPE: Device data2 activated. > > In the boot messages (device names will vary - I'm using two 300GB USB > drives) > > > - There is a .snap directory on the volume. Is this used by gstripe? Nope > that's a ufs2 thing > > > - I used newfs -O 2 to create a UFS2 file system on the volume. Is this > treated like any other UFS2 volume that can utilize fsck, etc? Yes - > although you might want to specify a block size as the defaults tend to > assume lots of small files which is not always the case for very large > stripe sets. > > - How resiliant is this volume if the system were to crash? The same as any > other volume except that you have twice the chance of a hard drive failure > which would be fatal to the volume. > > --Thanks! Nick > > On Tue, 15 Mar 2005 23:48:39 +0100, Andrea Venturoli > wrote: > Nick Pavlica wrote: > All, I would like to set up a raid 0 volume on my 5.3 server using two > identical SATA drives. After reading through a number of documents I noticed > that there are two related utilities to do this, Vinum and Gvinum. Which > utility should be used? It's my understanding that Gvinum is the most > current and should be used on 5.3+? Does the hadbook refer to Vinum, Gvinum > or both? I'd reccomend you none of them; look here for detailed reasons: > http://people.freebsd.org/~rse/mirror/. In brief, I've experienced severe > panics with vinum after an upgrade from 5.2.1 to 5.3 and gvinum is marked as > alpha software and poorly documented. I'm quite happy with gmirror now, > which the tutorial above describes. You would use gstripe instead. bye av. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, > send any mail to "freebsd-questions-unsubscribe@freebsd.org"