From owner-freebsd-current@FreeBSD.ORG Mon May 5 08:30:20 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 5EBBD37B421 for ; Mon, 5 May 2003 08:30:20 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDA7543F3F for ; Mon, 5 May 2003 08:30:19 -0700 (PDT) (envelope-from nectar@nectar.cc) Received: by gw.nectar.cc (Postfix, from userid 1001) id B20A726; Mon, 5 May 2003 10:30:18 -0500 (CDT) Date: Mon, 5 May 2003 10:30:18 -0500 From: "Jacques A. Vidrine" To: freebsd-current@FreeBSD.org Message-ID: <20030505153018.GA28343@hellblazer.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Url: http://www.celabo.org/ Subject: Today's -CURRENT, vinum damage 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: Mon, 05 May 2003 15:30:20 -0000 Hi Folks, I cvsup'd this morning, and built/installed a new -CURRENT. (I was previously running circa morning April 29.) I was greeted by WARNING: Expected rawoffset 63, found 0 which seemed harmless enough (I only mention it in passing). When attempting to start Vinum, the `vinum' process became stuck & unkillable in biord. Has anyone else seen this? I loaded my old kernel and I am trying to recover by rebuilding a morning of 2003/05/04 world. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se