kern/60235: some /dev-entries missing for newly auto-added disks

[Mikhail Teterin]

>Number:         60235
>Category:       kern
>Synopsis:       some /dev-entries missing for newly auto-added disks
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec 14 12:10:20 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Mikhail Teterin
>Release:        FreeBSD 5.2-BETA i386
>Organization:
Virtual Estates, Inc.
>Environment:
System: FreeBSD aldan.algebra.com 5.2-BETA FreeBSD 5.2-BETA #4: Mon Nov 24 22:24:34 EST 2003 root at aldan.algebra.com:/ccd/obj/ccd/src/sys/DEBUG i386

>Description:
	When I connect the USB flash card reader, FreeBSD detects it
	properly and the new /dev/da3 is added. However, the /dev/da3s1
	is missing, even though fdisk lists 4 slises on the device:
	******* Working on device /dev/da3 *******
	parameters extracted from in-core disklabel are:
	cylinders=488 heads=64 sectors/track=32 (2048 blks/cyl)

	parameters to be used for BIOS calculations are:
	cylinders=488 heads=64 sectors/track=32 (2048 blks/cyl)

	Media sector size is 512
	Warning: BIOS sector numbering starts with sector 1
	Information from DOS bootblock is:
	The data for partition 1 is:
	sysid 6 (0x06),(Primary 'big' DOS (>= 32MB))
	    start 63, size 999873 (488 Meg), flag 80 (active)
		beg: cyl 0/ head 1/ sector 1;
		end: cyl 991/ head 15/ sector 63
	The data for partition 2 is:
	<UNUSED>
	The data for partition 3 is:
	<UNUSED>
	The data for partition 4 is:
	<UNUSED>

	Trying to mount it fails at first:

	% mount -oro -t msdos /dev/da3s1 /sandisk
	msdosfs: /dev/da3s1: No such file or directory

	But succeeds after the following chicken-waiving:

	% mount -oro -t msdos /dev/da3 /sandisk
	msdosfs: /dev/da3: Invalid argument
	% mount -oro -t msdos /dev/da3s1 /sandisk
	%

	So, even though the attempt to mount /dev/da3 directly fails
	(as expected), it somehow creates the missing da3s1, so that
	the subsequent attempt to mount it finaly succeeds.

	The files are nicely accessible after this and everything else
	seems to work.

>How-To-Repeat:

	See description

>Fix:

	See description
>Release-Note:
>Audit-Trail:
>Unformatted: