Date: Sun, 03 Oct 1999 12:42:54 -0700 From: Jake Burkholder <jake@checker.org> To: Christopher Masto <chris@netmonger.net> Cc: current@FreeBSD.ORG Subject: Re: SOLVED (partly): Re: Can't start vinum with new kernels Message-ID: <19991003194254.5C2911FD7@io.yi.org> In-Reply-To: Your message of "Sun, 03 Oct 1999 15:09:02 EDT." <19991003150902.A15336@netmonger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I found out what was causing "Can't get device list: Cannot allocate > memory".. libdevstat mismatch. > > Now I'm getting a panic, but hopefully I'll have a decent backtrace > out of it soon. I ran into to that too and thought I was screwed, but vinum read worked. I built the new kernel rebuilt modules rebuilt /sbin/vinum rebooted...Can't get device list: Cannot allocate memory...single user mode vinum read /dev/wd0 /dev/wd1 exit then promptly rebuilt the world, and everything was fine. the panic could be from old /sbin/vinum with new kernel and/or vinum.ko, I'd suggest rebuilding that too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991003194254.5C2911FD7>