Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Mar 2005 16:15:41 -0700
From:      Nick Pavlica <linicks@gmail.com>
To:        John Pettitt <jpp@cloudview.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD 5.3+ Vinum or Gvinum
Message-ID:  <dc9ba04405031615152279ae08@mail.gmail.com>
In-Reply-To: <4238A904.6040801@cloudview.com>
References:  <dc9ba044050315130133af7f05@mail.gmail.com> <42376647.4030008@netfence.it> <dc9ba04405031613316752c044@mail.gmail.com> <4238A904.6040801@cloudview.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <jpp@cloudview.com> 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 <ml@netfence.it>
> 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"



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