From owner-freebsd-bugs Wed Apr 8 06:23:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02067 for freebsd-bugs-outgoing; Wed, 8 Apr 1998 06:23:23 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01950; Wed, 8 Apr 1998 06:21:47 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA24407; Wed, 8 Apr 1998 23:18:19 +1000 Date: Wed, 8 Apr 1998 23:18:19 +1000 From: Bruce Evans Message-Id: <199804081318.XAA24407@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.ORG, FreeBSD-gnats@FreeBSD.ORG, woods@zeus.leitch.com Subject: Re: kern/6242: vnode disk driver too unstable in -STABLE to "make release" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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. >That the vnode disk driver blows up when you over-fill its filesystem is >only a side-effect to the real problem here. 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. 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message