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_at_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). 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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC