From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 04:18:44 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 C486D16A4CE for ; Sat, 24 Jul 2004 04:18:44 +0000 (GMT) Received: from web14206.mail.yahoo.com (web14206.mail.yahoo.com [216.136.173.70]) by mx1.FreeBSD.org (Postfix) with SMTP id A966A43D41 for ; Sat, 24 Jul 2004 04:18:44 +0000 (GMT) (envelope-from mariodoria@yahoo.com) Message-ID: <20040724041844.41697.qmail@web14206.mail.yahoo.com> Received: from [200.56.121.197] by web14206.mail.yahoo.com via HTTP; Fri, 23 Jul 2004 21:18:44 PDT Date: Fri, 23 Jul 2004 21:18:44 -0700 (PDT) From: Mario Doria To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Vinum status 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: Sat, 24 Jul 2004 04:18:44 -0000 Hi, I have a box which I use to play around with freebsd-current, it has a large mirrored vinum setup and that is why I want to know if anybody out there is running recent -CURRENT sources. Specifically, I'm interested in knowing if the "panic: dangling vnode" problem is still aroud; also, if by doing "vinum start" and "vinum stop" repeatedly, the vinum config reports a disk as crashed. Thanks Mario Doria