From owner-freebsd-questions@FreeBSD.ORG Thu Jul 14 15:25:03 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 B1B5416A41C for ; Thu, 14 Jul 2005 15:25:03 +0000 (GMT) (envelope-from kl@os.lv) Received: from krauklis.latnet.lv (krauklis.latnet.lv [159.148.19.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C77E43D46 for ; Thu, 14 Jul 2005 15:24:58 +0000 (GMT) (envelope-from kl@os.lv) Received: from localhost (localhost.localdomain [127.0.0.1]) by krauklis.latnet.lv (Postfix) with ESMTP id 63C651EFCC2; Thu, 14 Jul 2005 18:24:57 +0300 (EEST) Received: from krauklis.latnet.lv ([127.0.0.1]) by localhost (krauklis.latnet.lv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18581-25; Thu, 14 Jul 2005 18:24:56 +0300 (EEST) Received: from os.lv (unknown [159.148.155.3]) by krauklis.latnet.lv (Postfix) with SMTP id B6E7D1EFCF2; Thu, 14 Jul 2005 18:24:46 +0300 (EEST) Received: from 80.70.26.44 ([80.70.26.44]) by os.lv (WinRoute Pro 4.1) with SMTP; Thu, 14 Jul 2005 18:27:10 +0300 Message-ID: <42D683BC.4010602@os.lv> Date: Thu, 14 Jul 2005 18:24:44 +0300 From: Casper User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Kelly , freebsd-questions@freebsd.org References: <42D6683E.7040406@os.lv> <58488053-6525-49BB-846A-03845A162020@amadeus.demon.nl> <20050714144907.GA24229@Grumpy.DynDNS.org> In-Reply-To: <20050714144907.GA24229@Grumpy.DynDNS.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at latnet.lv Cc: Subject: Re: FreeBSD 5.x raid... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 15:25:03 -0000 David Kelly wrote: > On Thu, Jul 14, 2005 at 03:55:38PM +0200, FreeBSD questions mailing list wrote: > >>'plex org raid1 512k' is invalid >>you should use: >>'plex org concat' > > > Uh, he wants all data on one SATA drive and a mirror on the other. > Therefore he does not want to "concat" but to "mirror". The man page > examples often complicatate things by concating some drives then > mirroring the concated. Yep, thanx, I have changed: drive a device /dev/ad4c drive b device /dev/ad6c volume www plex org mirror sd length 165g drive a sd length 165g drive b but: vinum create -f www.vinum 4: plex org mirror ** 4 Invalid plex organization: Invalid argument 5: sd length 165g drive a ** 5 Unnamed sd is not associated with a plex: Invalid argument 6: sd length 165g drive b ** 6 Unnamed sd is not associated with a plex: Invalid argument 2 drives: D a State: up /dev/ad4c A: 190782/190782 MB (100%) D b State: up /dev/ad6c A: 190782/190782 MB (100%) 1 volumes: V www State: down Plexes: 0 Size: 0 B 0 plexes: 0 subdisks: > Vinum is flaky on 5.x, while gvinum works pretty good. Others have > suggested the future is brighter with the RAID functions in GEOM but I'm > not yet ready to experiment with my 300G gvinum slice. > > I never quite figured out the manual method of configuring [g]vinum. The > "SIMPLIFIED CONFIGURATION" section of the manual got me running. I think > this how he would want to do it. > > There isn't a gvinum man page. Gvinum (GEOM vinum) lacks complete vinum > functionality but I don't know what. > > First, I don't think its wise to use partition "c". Use sysinstall to > create the single largest partition possible and it'll be on "d". > Partition "c" has special meaning and many times its used because the > device driver fakes a disk label with "c" when a real disk label is > missing. If the driver is always able to fake a correct and identical > label then you are fine, but its better to write a real one on disk. > > Creating a gvinum mirror is as simple as this: > > # gvinum mirror -v /dev/ad4d /dev/ad6d > > Might need: > # gvinum start > > Then edit /etc/rc.d./vinum and add the "g" to this line thusly: > > start_cmd="gvinum start" > > Your new slice will probably be /dev/gvinum/vinum0, so edit /etc/fstab > appropriately. > > The slice should be ready for newfs, and then mounting. > > Be sure to add this to /etc/rc.conf: > start_vinum="YES" >