Date: Wed, 8 Apr 1998 11:32:25 -0400 (EDT) From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-bugs@FreeBSD.ORG Cc: FreeBSD-gnats@FreeBSD.ORG Subject: Re: kern/6242: vnode disk driver too unstable in -STABLE to "make release" Message-ID: <199804081532.LAA25182@brain.zeus.leitch.com> In-Reply-To: Bruce Evans's message of "Wed, April 8, 1998 23:18:19 %2B1000" regarding "Re: kern/6242: vnode disk driver too unstable in -STABLE to "make release"" id <199804081318.XAA24407@godzilla.zeta.org.au> References: <199804081318.XAA24407@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Wed, April 8, 1998 at 23:18:19 (+1000), Bruce Evans wrote: ] > Subject: Re: kern/6242: vnode disk driver too unstable in -STABLE to "make release" > > >Ah ha. It seems for some reason that the fixit floppy stuff has grown > >too large to fit on a floppy, at least in my local build environment. > > The newfs options could be optimised for space a bit more. I'll try that! Thanks! > FIlling up the file system on a vn device seems to be harmless in > -current. However, `vnconfig -u' before umount is permitted and gives > the bizarre mountpoint properties mentioned in the PR. Ah ha! > doFS.sh is executed by `sh -e', so when the file system fills up, the > build aborts without either unmounting or `vnconfig -u'ing the device. > It is then easy to forget to unmount the device before unconfiguring > it. Except I don't run "vnconfig -u" either. Perhaps it unconfigures itself when it encounters this ``fatal'' error of being filled up? At least now I think I know how to resurrect the running system without needing a reboot.... -- Greg A. Woods +1 416 443-1734 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804081532.LAA25182>