FreeBSD 7.0 Mount Strangeness

Julian Stacey jhs at
Sat Jun 7 12:20:21 UTC 2008

> From:		dfeustel at 
> Date:		Sat, 7 Jun 2008 03:20:13 +0000 (UTC) 
> Message-id:	<20080607032014.0521B8FC1A at> 

dfeustel at wrote:
> I have encountere what seems to be strangeness in the way mount works
> when mounting msdos file systems on usb mass storage devices.  I have a
> 14-in-one usb reader connected to my computer running AMD 64-bit FreeBSD
> 7.0 release. At boot, there are four special files in /dev for the usb
> devices: /dev/da[0-3]. All attempts to mount an msdos file system using
> the command "mount -t msdosfs /dev/daNs1 /mnt" fail with the message "no
> such file or directory". Checking /dev, there are no special files of
> the form daNs1. If I then do "mount -t msdosfs /dev/daN" I get the
> message "invalid argument", BUT there is now in the /dev directory an
> entry daNs1, and the next "mount -t /dev/daNs1 /mnt" command succeeds
> :-).  This behavior is repeated for each mount of an msdos file system
> on a previously unused device socket on the usb reader. The newly
> created devices remain after they are unmounted, so this problem goes
> away until reboot, at which time the device files of form daNs1 are
> deleted. 
> I have not found any FreeBSD documentation of this behavior yet. 
> Is this behavior known and expected? (I'm a FreeBSD newbie.)

Behaviour is known. Same on 6.2 as well.  Both on i386 & amd64.
In my 6 usbd.conf & 7 devd.conf I have dummy reads to first trigger
creation of extra devices.

> Thanks,
> Dave Feustel
> _______________________________________________
> freebsd-amd64 at mailing list
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at"

Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich
	Mail just Ascii plain text.  HTML & Base64 text are spam.

More information about the freebsd-amd64 mailing list