From owner-freebsd-current@FreeBSD.ORG Wed Aug 25 20:21:13 2004 Return-Path: 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 242B416A4DA for ; Wed, 25 Aug 2004 20:21:13 +0000 (GMT) Received: from mail.tecdigital.net (mail.tecdigital.net [69.20.85.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 050F243D41 for ; Wed, 25 Aug 2004 20:21:13 +0000 (GMT) (envelope-from mariodoria@yahoo.com) Received: from madd-wireless.localdomain (host-200-56-121-254.block.alestra.net.mx [200.56.121.254]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.tecdigital.net (Postfix) with ESMTP id 354E649FA4 for ; Wed, 25 Aug 2004 15:21:12 -0500 (CDT) From: "Mario A. Doria" To: freebsd-current@freebsd.org Date: Wed, 25 Aug 2004 15:21:10 -0500 User-Agent: KMail/1.7 References: <20040825195832.6A29D16A523@hub.freebsd.org> In-Reply-To: <20040825195832.6A29D16A523@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408251521.11019.mariodoria@yahoo.com> Subject: Re: freebsd-current Digest, Vol 73, Issue 14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 25 Aug 2004 20:21:13 -0000 > Yes, I meant 5.3 :-) > > So what's state is (g)vinum likely to be in for 5.3? I'm hesitant to > upgrade because it appears that the system is moving from under > vinum's feet, and gvinum isn't there yet. What are people who are > currently using vinum on earlier 5.x's going to do until gvinum is > finished? Well, I have two machines running RELENG_5 from yesterday. One machine has four SCSI disks, two in a concatenated volume and two in a mirrored volume. I created everything in vinum, rebooted and reloaded in gvinum, no problems. This machine has been running make -j16 buildworlds on that volume for the last 36 hours. In another, I had two disks with a concatenated volume, and because I had two vinum drives in each disk, all hell broke loose. It wouldn't recognize the proper size of the volume, lose information, report disks as crashed and after a reboot, report everything was fine. I could reconfigure the vinum configuration using "vinum", and it would run OK until a reboot. Now I only have one vinum drive per disk, but still I have problems. I'm going to reformat the disks and start over. Mario