From owner-freebsd-current Sun Oct 29 22:38:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 6373A37B479; Sun, 29 Oct 2000 22:38:39 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id RAA07515; Mon, 30 Oct 2000 17:38:34 +1100 Date: Mon, 30 Oct 2000 17:38:21 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "John W. De Boskey" Cc: Current List , Adrian Chadd Subject: Re: vinum & fsck wrappers strangeness In-Reply-To: <20001029215454.A60321@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Oct 2000, John W. De Boskey wrote: > I ran into an interesting gotcha with fsck and vinum... > > I have the following line in /etc/fstab: > > /dev/vinum/raid5 /pub ufs rw 2 2 > > and during an upgrade (old current to current), I commented the > line out during the reboot process. After bringing the new system > online, I executed: > > /sbin/fsck -y /dev/vinum/raid5 > > and received the following error: > > fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory I saw a related problem with mfs. I had the following lines in /etc/fstab: --- #/dev/ad0s4 none swap sw /dev/ad0s4 /tmp mfs rw,-s65536,-i8192,noatime,noauto --- The mfs line has very little to do with /dev/ad0s4 or swap. The label for /dev/ad0s4 just provides a (bogus) geometry for mfs. I wasn't using /dev/ad0s4 for either swap or mfs, but it happened to have a filesystem on it, and when I tried to fsck this, fsck attempted to exec the nonexistent file fsck_mfs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message