From owner-freebsd-current@FreeBSD.ORG Mon Jan 5 08:51:09 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 1C29A16A4CF for ; Mon, 5 Jan 2004 08:51:09 -0800 (PST) Received: from catwoman.cs.moravian.edu (catwoman.cs.moravian.edu [204.186.193.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF71043D46 for ; Mon, 5 Jan 2004 08:51:07 -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 i05Gp6w14785; Mon, 5 Jan 2004 11:51:06 -0500 (EST) Date: Mon, 5 Jan 2004 11:51:06 -0500 (EST) Message-Id: <200401051651.i05Gp6w14785@catwoman.cs.moravian.edu> From: Stephen Corbesero To: freebsd-current@freebsd.org Subject: is vinum in current working for anyone 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: Mon, 05 Jan 2004 16:51:09 -0000 I have been unable to use vinum in current since about 5.1. I have just sent debugging information to Greg Lehey, but I was wondering if it is working for anyone and how our configurations differ. If rc.conf specifies vinum_start="YES", my system usually crashes as soon as vinum loads and starts scanning disks. Sometimes it doesn't crash, but the vinum config is lost on at least one of the vinum drives. -- Stephen Corbesero Associate Professor of Computer Science Moravian College, Bethlehem, PA 18018