From owner-freebsd-geom@FreeBSD.ORG Mon Nov 5 17:36:55 2007 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0769E16A41A for ; Mon, 5 Nov 2007 17:36:55 +0000 (UTC) (envelope-from freebsd-lists@ideo.com.br) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id AD87F13C491 for ; Mon, 5 Nov 2007 17:36:53 +0000 (UTC) (envelope-from freebsd-lists@ideo.com.br) Received: by py-out-1112.google.com with SMTP id u77so3341490pyb for ; Mon, 05 Nov 2007 09:36:43 -0800 (PST) Received: by 10.65.53.3 with SMTP id f3mr13551205qbk.1194284202336; Mon, 05 Nov 2007 09:36:42 -0800 (PST) Received: by 10.65.137.2 with HTTP; Mon, 5 Nov 2007 09:36:42 -0800 (PST) Message-ID: <8d4842b50711050936n24ff27c4uc9df10c6bffa1a3a@mail.gmail.com> Date: Mon, 5 Nov 2007 15:36:42 -0200 From: "Marco Haddad" To: "Ulf Lilleengen" In-Reply-To: <20071103015435.GB22755@stud.ntnu.no> MIME-Version: 1.0 References: <8d4842b50710310814w3880f7d3ldf8abe3a236cbcc8@mail.gmail.com> <20071031215756.GB1670@stud.ntnu.no> <472AA59F.3020103@rootnode.com> <0001DFFC-0115-1000-9A80-3F81219C1B16-Webmail-10013@mac.com> <8d4842b50711021832g7ad7cec9x48d2f114b1e41f5f@mail.gmail.com> <20071103015435.GB22755@stud.ntnu.no> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Joe Koberg , Peter Giessel , freebsd-geom@freebsd.org Subject: Re: gvinum and raid5 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: Mon, 05 Nov 2007 17:36:55 -0000 On 11/2/07, Ulf Lilleengen wrote: > > On fre, nov 02, 2007 at 10:32:54 -0300, Marco Haddad wrote: > [...] > > I think there's no easier way... > > Yes there is. Replacing a drive in gvinum follows the following procedure: > 1. Create config for the new drive and name the drive _differently_ than > the > old one. > > 2. Use the gvinum 'move' command to move the stale subdisk to the new > drive. > > 3. Make sure the the subdisk now points to the new drive and that it's in > the > 'stale' state. > > 4. Start the plex (gvinum start). > > The other issues you encountered have been fixed in my gvinum work this > summer. Also, replacing a drive and rebuilding a plex can happen without > unmounting your volume in the new gvinum. Well, I can't do that because 'gvinum create' panics even if the new drive is named differently. Perhaps the problem is using the same device which was once already present, and that's why I need to remove all objects first... The fact is I can't remove the objects with the system running, and once they are removed, there's no need for a different name. Actually, it's easier to use the same original create script... I'll try to apply your patches and see if it this issue is solved. Thanks, Marco Haddad