From owner-freebsd-current@FreeBSD.ORG Mon Jul 11 17:19:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF02416A41F for ; Mon, 11 Jul 2005 17:19:17 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F41F43D45 for ; Mon, 11 Jul 2005 17:19:17 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.12.9) with ESMTP id j6BHJFZs020033 for ; Mon, 11 Jul 2005 19:19:15 +0200 (CEST) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.1/8.12.9/Submit) id j6BHJFDD020032 for freebsd-current@freebsd.org; Mon, 11 Jul 2005 13:19:15 -0400 (EDT) (envelope-from cracauer) Date: Mon, 11 Jul 2005 13:19:15 -0400 From: Martin Cracauer To: freebsd-current@freebsd.org Message-ID: <20050711131915.A19863@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: gvinum. A little worse than I thought :-) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2005 17:19:18 -0000 I understand that gvinum doesn't have documentation yet, and I found a note "or basic stuff (like creating concatinated volumes) you can use the vinum documentation and replace 'vinum' with 'gvinum' when you try things." But this is going a bit far: sbin/gvinum(grisu)80# gvinum gvinum -> help [...] info [-v] [-V] List information about volume manager state. [...] gvinum -> info unknown command 'info' gvinum -> dumpconfig unknown command 'dumpconfig' Also, seperate issue, the geom_vinum kernel module is not unloadable but the "stop" command tries to do exactly that, and fails. What the stop command does not do is actually stop or detach anything, so I am stuck with 3 devices captive in a failed raid5 setup attempt until I reboot. gvinum -> stop raid gvinum: cannot unload geom_vinum: Operation not supported gvinum -> stop raid.lp0 gvinum: cannot unload geom_vinum: Operation not supported gvinum -> stop gvinum: cannot unload geom_vinum: Operation not supported The detach command, listed in help, is also only triggering a message that it is unsupported. But have no fear, I just poked a little deeper into Linux raid (raid5) and it was way worse :-) What is a recommended ATA or SATA controller with hardware RAID5 and the capability to run different RAID levels on different parts of the disk these days? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ No warranty. This email is probably produced by one of my cats stepping on the keys. No, I don't have an infinite number of cats.