From owner-freebsd-stable@FreeBSD.ORG Fri Dec 1 16:56:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 215C416A412 for ; Fri, 1 Dec 2006 16:56:08 +0000 (UTC) (envelope-from flash@cs.moravian.edu) Received: from catwoman.cs.moravian.edu (catwoman.cs.moravian.edu [204.186.193.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FAB343CAD for ; Fri, 1 Dec 2006 16:55:51 +0000 (GMT) (envelope-from flash@cs.moravian.edu) Received: from lantern.cs.moravian.edu (lantern.cs.moravian.edu [204.186.196.23]) by catwoman.cs.moravian.edu (8.11.7p1+Sun/8.11.7) with ESMTP id kB1Gu6p21307 for ; Fri, 1 Dec 2006 11:56:06 -0500 (EST) Received: from lantern.cs.moravian.edu (localhost [127.0.0.1]) by lantern.cs.moravian.edu (8.13.4/8.13.4) with ESMTP id kB1Gu6p0086637 for ; Fri, 1 Dec 2006 11:56:06 -0500 (EST) (envelope-from flash@lantern.cs.moravian.edu) Received: (from flash@localhost) by lantern.cs.moravian.edu (8.13.4/8.13.4/Submit) id kB1Gu6fQ086634; Fri, 1 Dec 2006 11:56:06 -0500 (EST) (envelope-from flash) Date: Fri, 1 Dec 2006 11:56:06 -0500 (EST) Message-Id: <200612011656.kB1Gu6fQ086634@lantern.cs.moravian.edu> From: Stephen Corbesero To: freebsd-stable@freebsd.org Subject: Gvinum functionality 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: Fri, 01 Dec 2006 16:56:08 -0000 I have a machine that has been functioning as a news and anonymous ftp server. This machine was running FreeBSD-5 using vinum on four 200GB firewire drives. The vinum configuration was always a little flaky because, but it was generally okay if I didn't try to make changes. About three weeks ago, one of the drives failed and I used that as an excuse to update the machine to FreeBSD6-stable and switch from the old vinum to the GEOM based gvinum. In the process of doing the upgrades and restores, I built volumes with only one plex to start, with the intention of adding the second plex to complete the mirror once everything was back in place. I have been unable to do this. The attach command is not yet implemented in gvinum. I tried to create with the new plex listed as being part of the volume, but that didn't work well either. First, I forgot to fully name the pieces and ended up with a volume home that had the following components volume home plex home.p0 sd home.p0.s0 sd home.p0.s1 plex .p0 sd .p0.s0 sd .p0.s1 Despite the unusual naming scheme, this would have been okay, but it actually killed my home volume. The new plex (.p0) started as "up", and I am sure its contents were inconsistent. I didn't see any way to "synchronize" , and I would have been afraid to because how would it know which plex was the good data. Needless to say, getting rid of .p0, .p0.s0, and .p0.s1 was quite an adventure. Luckily, a printconfig revealed that the objects names had a leading ^S. So, I am back to my original problem. How do I create a new plex and then attach it to a existing volume AND have the new plex's data synchronized with the existing (good) plex. This would seem like a crucial part of a volume management system, otherwise recovery from a disk failure might be impossible. Any suggestions? -- Stephen Corbesero This message brought to you by Associate Professor of Computer Science -- electrons -- Moravian College, Bethlehem, PA 18018 The Other Charged Particle