From owner-freebsd-stable@FreeBSD.ORG Mon Apr 10 13:33:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 015B416A400 for ; Mon, 10 Apr 2006 13:33:50 +0000 (UTC) (envelope-from freebsd4@fadesa.es) Received: from fuego.fadesa.es (fuego.fadesa.es [195.55.55.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D53843D66 for ; Mon, 10 Apr 2006 13:33:42 +0000 (GMT) (envelope-from freebsd4@fadesa.es) Received: (from root@localhost) by fuego.fadesa.es (8.9.3p2/8.8.8) id PAA08269 for ; Mon, 10 Apr 2006 15:34:51 +0200 Received: from tierra.fadesa.es(195.55.55.7) by fuego.fadesa.es Mon, 10 Apr 06 15:34:24 +0200 Received: from fadesa.es (filemon.fadesa.es [195.55.55.6] (may be forged)) by tierra.fadesa.es (8.9.3p2/8.8.8) with ESMTP id PAA20201 for ; Mon, 10 Apr 2006 15:32:58 +0200 Sender: fan@fadesa.es Message-ID: <443A5E8A.FBFABB3F@fadesa.es> Date: Mon, 10 Apr 2006 15:32:58 +0200 From: "=?iso-8859-15?Q?Jos=E9?= M. =?iso-8859-15?Q?Fandi=F1o?=" Organization: Inmobiliaria FADESA X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.30-ow1 i686) X-Accept-Language: gl, en, es MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4433DB2B.7753D2C3@fadesa.es> <20060406153115.GC5578@garage.freebsd.pl> <44354FB1.6163DF7A@fadesa.es> <4436199E.3E019AD4@fadesa.es> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-Logged: Logged by tierra.fadesa.es as PAA20201 at Mon Apr 10 15:32:58 2006 Subject: Re: GEOM_RAID3: Device datos is broken, too few valid components X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 13:33:50 -0000 Hello, > > Pawel Jakub Dawidek wrote: > > > You should be safe as long as the order of slices you give here is the > > > same as it was when device was initially labeled. I have follow this procedure and it worked for me: select "6. Escape to loader prompt" OK unload OK disable-module geom_raid3 OK boot -s # fsck -p # mount -a # graid3 dump ad4s2 | grep -w no # graid3 dump ad5s2 | grep -w no # graid3 dump ad6s2 | grep -w no (this will give you the right order to use with the next command) # graid3 label -h ad5s2 ad6s2 ad4s2 # graid3 load # graid3 remove -n 0 datos # graid3 insert -n 0 datos ad5s2 now, all is working as expected. However I'm curious about the missing flag "HARDCODED" for ad5s2. is it reasonable to ignore this missing flag? # grai3 list Geom name: datos State: COMPLETE Components: 3 Flags: ROUND-ROBIN GenID: 0 SyncID: 1 ID: 1391160618 Providers: 1. Name: raid3/datos Mediasize: 311491352576 (290G) Sectorsize: 1024 Mode: r1w1e1 Consumers: 1. Name: ad4s2 Mediasize: 155745676800 (145G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY, HARDCODED GenID: 0 SyncID: 1 Number: 2 Type: PARITY 2. Name: ad5s2 Mediasize: 155745676800 (145G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 1 Number: 0 Type: DATA 3. Name: ad6s2 Mediasize: 155745676800 (145G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY, HARDCODED GenID: 0 SyncID: 1 Number: 1 Type: DATA -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d- s+:+() a32 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++ G++ e- h+(++) !r !z ------END GEEK CODE BLOCK------