Re: Today's -CURRENT, vinum damage

From: Robert Watson <rwatson_at_FreeBSD.org>
Date: Mon, 5 May 2003 11:46:39 -0400 (EDT)
On Mon, 5 May 2003, Jacques A. Vidrine 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?

It might be useful (and perhaps even instructive) to generate a stack
trace for that kernel process.  You can do this by breaking into DDB and
using the trace command on the specific pid (i.e., trace 9).

> I loaded my old kernel and I am trying to recover by rebuilding a
> morning of 2003/05/04 world.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert_at_fledge.watson.org      Network Associates Laboratories
Received on Mon May 05 2003 - 06:46:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC