From owner-freebsd-current@FreeBSD.ORG Tue Dec 30 11:15:46 2003 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 D12D716A4CE for ; Tue, 30 Dec 2003 11:15:46 -0800 (PST) Received: from catwoman.cs.moravian.edu (catwoman.cs.moravian.edu [204.186.193.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D97B43D1D for ; Tue, 30 Dec 2003 11:15:45 -0800 (PST) (envelope-from flash@cs.moravian.edu) Received: (from flash@localhost) by catwoman.cs.moravian.edu (8.11.7+Sun/8.9.3) id hBUJFik10597; Tue, 30 Dec 2003 14:15:44 -0500 (EST) Date: Tue, 30 Dec 2003 14:15:44 -0500 (EST) Message-Id: <200312301915.hBUJFik10597@catwoman.cs.moravian.edu> From: Stephen Corbesero To: freebsd-current@freebsd.org Subject: vinum experimentation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: corbesero@cs.moravian.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2003 19:15:46 -0000 I hope this is information is useful. I am really hoping to have a working vinum in FreeBSD 5.x. As we all know, vinum has been cranky for a little while now. It seemed to work fine for me in the early 5.0's, but went 'south" sometime as the 5.1's began coming out. I have been playing with it on a couple of machines at work, and I have noticed the following behaviors. I am mostly playing with mirroring some volumes on two IDE drives. * If I start vinum manually after the system is up, and shut it down manually before I do a reboot, the configuration seems to survive just fine. On the next boot, I can again start vinum manually, the drives are read, and I can mount the partitions. * If I let vinum come up automatically (setting start_vinum="YES" in rc.conf), then one of the following will happen. a) a system panic before the boot process is completed b) at least one of the vinum can not be found, so anything that drive is down/faulty. did discover, however, that if I recreate the drive in vinum, the plexes cheerfully come back. c) the vinum drives can be found, but no volumes are defined anymore * If I manually shut vinum down before rebooting, but let the system start it automatically, the same problems (a..c) occur as described in the previous bullet If this is useful, and someone would like more information, I'll be happy to continue my experiments. My systems are rather generic. -- Stephen Corbesero Associate Professor of Computer Science Moravian College, Bethlehem, PA 18018