From owner-freebsd-current@FreeBSD.ORG Tue May 6 12:54:25 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 595AF37B401; Tue, 6 May 2003 12:54:25 -0700 (PDT) Received: from MX3.estpak.ee (mta2.mail.neti.ee [194.126.101.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B764643FA3; Tue, 6 May 2003 12:54:23 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-34-165-dsl.mus.estpak.ee [80.235.34.165]) by MX3.estpak.ee (Postfix) with ESMTP id A1D6B881D3; Tue, 6 May 2003 22:54:21 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h46CsK9x000871; Tue, 6 May 2003 15:54:20 +0300 (EEST) (envelope-from vallo) Date: Tue, 6 May 2003 15:54:20 +0300 From: Vallo Kallaste To: "Greg 'groggy' Lehey" Message-ID: <20030506125420.GA697@kevad.internal> References: <20030505153018.GA28343@hellblazer.celabo.org> <20030505164843.GB17679@madman.celabo.org> <20030506052545.GE52037@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030506052545.GE52037@wantadilla.lemis.com> User-Agent: Mutt/1.5.4i-ja.1 cc: "Jacques A. Vidrine" cc: freebsd-current@FreeBSD.org Subject: Re: HEADS UP: Today's -CURRENT, vinum damage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 19:54:25 -0000 On Tue, May 06, 2003 at 02:55:45PM +0930, Greg 'groggy' Lehey wrote: > >> 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. > > > > The `morning of 2003/05/04' world works. I will try again in a couple > > of days, and get some more debug info if the problem persists. > > Is anybody else having trouble with recent Vinum? If so, please let > me know as soon as possible. It's broken. I had to do some repairwork to get my /usr back up just moments ago. The May 6 kernel and userland from ~17:30 UTC hangs at boot while trying to start vinum (scan disks). May 1 kernel and May 6 userland will not play together, complains about some ioctl. I had to boot Windows and download older vinum(8) binary from JPSNAP livetree. I don't want to see such things in the supposedly _BETA_ software. This isn't BETA, it's some weird breed if I can name it. Ugh. -- Vallo Kallaste