Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 May 2003 10:53:33 +0930
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Vallo Kallaste <kalts@estpak.ee>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: HEADS UP: Today's -CURRENT, vinum damage
Message-ID:  <20030507012333.GX52037@wantadilla.lemis.com>
In-Reply-To: <20030506125420.GA697@kevad.internal>
References:  <20030505153018.GA28343@hellblazer.celabo.org> <20030505164843.GB17679@madman.celabo.org> <20030506052545.GE52037@wantadilla.lemis.com> <20030506125420.GA697@kevad.internal>

next in thread | previous in thread | raw e-mail | index | archive | help

--hNtiuZBcYkRjyNT4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tuesday,  6 May 2003 at 15:54:20 +0300, Vallo Kallaste wrote:
> On Tue, May 06, 2003 at 02:55:45PM +0930, Greg 'groggy' Lehey
> <grog@FreeBSD.org> 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).=20

Hmm.  That's the first I've heard of that one.  What happens if you
don't try to start Vinum at boot time?

> May 1 kernel and May 6 userland will not play together, complains
> about some ioctl.

Yes, that's a feature, not a bug.  You should never mix kernel and
userland of different ages, especially not in -CURRENT when work is
being done on a subsystem.

Greg
--
See complete headers for address and phone numbers

--hNtiuZBcYkRjyNT4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+uGAVIubykFB6QiMRAo+8AJkBoH//etQuu7PglHwlM3eprgCszQCgh+U7
Q8wBQxvFs7+RuJKM9nclv/A=
=5Yet
-----END PGP SIGNATURE-----

--hNtiuZBcYkRjyNT4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507012333.GX52037>