From owner-freebsd-current Thu Nov 2 1:17:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 485C337B4E5; Thu, 2 Nov 2000 01:17:50 -0800 (PST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eA29I3Y15316; Thu, 2 Nov 2000 10:18:03 +0100 (CET) (envelope-from adrian) Date: Thu, 2 Nov 2000 10:18:02 +0100 From: Adrian Chadd To: "John W. De Boskey" Cc: Current List Subject: Re: vinum & fsck wrappers strangeness Message-ID: <20001102101802.A15261@roaming.cacheboy.net> References: <20001029215454.A60321@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001029215454.A60321@FreeBSD.org>; from jwd@FreeBSD.ORG on Sun, Oct 29, 2000 at 09:54:54PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 29, 2000, John W. De Boskey wrote: > Hi, > > 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 OK. That means that the disklabel checks are failing for type 'vinum'. I'll take a look at this. What you should be doing is running fsck with a type, ie fsck -t ufs /dev/vinum/raid5 > So, it appears that fsck is attempting to determine a file > system type, tries to use /etc/fstab, and then falls back to > a secondary scheme. In the secondary scheme, ufs is what we want, > but vinum is what we're getting. > > If anyone has any information about this please let me know. I'll > try to look into it tomorrow. I'll try fix the autodetect for vinum partition types (if its possible, I seem to remember there being a vinum type in the header files). Its weird though, I would have thought a vinum device would be type FSTYPE (eg BSD4.3) rather than VINUM, which I'd associate with the underlying devices .. Adrian -- Adrian Chadd "Programming is like sex: One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message