On Sat, Jul 24, 2004 at 08:19:03PM +0200, Jens Schweikhardt wrote: > On Fri, Jul 23, 2004 at 09:18:44PM -0700, Mario Doria wrote: > ... > # Specifically, I'm interested in knowing if the "panic: dangling > # vnode" problem is still aroud; > > For the time being, you should be able to work around the panic > with a change in /etc/rc.d/vinum. Change > > start_cmd="vinum start" > to > start_cmd="mount /;vinum start" This is not without problems: [...] Mounting root from ufs:/dev/da0a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: kickstart. vinum: loaded vinum: reading configuration from /dev/da1e vinum: updating configuration from /dev/da2e vinum: updating configuration from /dev/da3e vinum: updating configuration from /dev/da4e swapon: adding /dev/da0b as swap device Starting file system checks: /dev/da0a: NO WRITE ACCESS /dev/da0a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Automatic file system check failed; help! Enter full pathname of shell or RETURN for /bin/sh: -- B.Walter BWCT http://www.bwct.de bernd_at_bwct.de info_at_bwct.deReceived on Sun Jul 25 2004 - 10:44:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:03 UTC