From owner-freebsd-geom@FreeBSD.ORG Fri May 4 00:14:00 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0CE016A404 for ; Fri, 4 May 2007 00:14:00 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (cust.95.160.adsl.cistron.nl [195.64.95.160]) by mx1.freebsd.org (Postfix) with ESMTP id 8844A13C44C for ; Fri, 4 May 2007 00:14:00 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.66 (FreeBSD)) (envelope-from ) id 1Hjl4B-000Fyf-9I; Fri, 04 May 2007 01:50:31 +0200 Message-ID: <463A7558.9090600@fluffles.net> Date: Fri, 04 May 2007 01:50:48 +0200 From: Fluffles User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: deniswork References: <1847971490.20070503223307@uzvik.kiev.ua> <971656.83802.qm@web30315.mail.mud.yahoo.com> <593515236.20070504022900@uzvik.kiev.ua> In-Reply-To: <593515236.20070504022900@uzvik.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?Arne_W=F6rner?= , freebsd-geom@freebsd.org Subject: Re: graid5 compilation problem X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2007 00:14:00 -0000 deniswork@uzvik.kiev.ua wrote: > Thanks, this help! > Another question: where graid5 store it settings? > Like other geom classes, geom_raid5 uses on-disk metadata to store all settings (stripesize, disk number, array size, array state, etc). You can view the stored metadata with command: graid5 dump ad4 (assuming ad4 is a graid5-disk) > I just wonder, can I remove some file, to clear up graid5 settings, > and create my raid in proper way. > To 'erase' these settings use "graid5 clear ad4". But remember that you cannot do this if the array is online; perhaps the easiest is making sure graid5 is not loaded automatically in /boot/loader.conf and then issuing a reboot. You can then clear all the disks which used to store metadata, and try again. Remember: you can still use the userland "graid5" binary utility even though the graid5 KLD-module is not loaded. This allows usage of the 'clear' command to achieve your goal. Good luck! - Veronica