Subject: bin/2979: fsck driver isn't so smart about picking fs type.
To: None <gnats-bugs@gnats.netbsd.org>
From: None <cgd@cs.cmu.edu>
List: netbsd-bugs
Date: 11/30/1996 14:37:02
>Number:         2979
>Category:       bin
>Synopsis:       fsck requires type to be given or fs to be in fstab
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 30 11:50:02 1996
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Kernel Hackers 'r' Us
>Release:        NetBSD-current, November 30, 1996
>Environment:
System: NetBSD bunnahabhain.pdl.cs.cmu.edu 1.2B NetBSD 1.2B (GENERIC) #271: Sat Nov 30 11:00:17 EST 1996 cgd@bunnahabhain.pdl.cs.cmu.edu:/usr/src/sys/arch/alpha/compile/GENERIC alpha


>Description:
	fsck requires either a type to be given or the file system to be
	mentioned in /etc/fstab, or it can't figure out which fsck back-end
	to use.

	This is bad, because fsck can do better.  It should at minimum
	try to get the disklabel from the device and see what the disklabel
	says is the type of the file system, and try that back-end.

>How-To-Repeat:
	create a new file system on a disk that's not mentioned in /etc/fstab.

	try to fsck that file system, by saying "fsck /dev/raw_device" where
	raw_device is the name of the device node used to access the device
	that contains the file system. 

	note that fsck says:
		fsck: /dev/raw_device: unknown special file or file system.

>Fix:
	A suggested fix is mentioned in the description.
>Audit-Trail:
>Unformatted: