From owner-freebsd-current@FreeBSD.ORG Sun Jul 1 19:44:06 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA7F016A468 for ; Sun, 1 Jul 2007 19:44:06 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id A89A213C469 for ; Sun, 1 Jul 2007 19:44:06 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 24652 invoked from network); 1 Jul 2007 19:44:07 -0000 Received: from ppp-71-139-42-13.dsl.snfc21.pacbell.net (HELO ?10.0.5.18?) (nate-mail@71.139.42.13) by root.org with ESMTPA; 1 Jul 2007 19:44:07 -0000 Message-ID: <46880400.70808@root.org> Date: Sun, 01 Jul 2007 12:44:00 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.4 (X11/20070617) MIME-Version: 1.0 To: current X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: GEOM weirdness with SD flash reader? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2007 19:44:06 -0000 Simply trying to mount a FAT filesystem in an external USB SD flash reader. The reader works fine, no errors in dmesg. deenlo# fdisk da2 ******* Working on device /dev/da2 ******* parameters extracted from in-core disklabel are: cylinders=982 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=982 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 243, size 2011917 (982 Meg), flag 0 beg: cyl 0/ head 3/ sector 55; end: cyl 998/ head 3/ sector 3 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: deenlo# mount -t msdosfs /dev/da2s1 /mnt/dos mount_msdosfs: /dev/da2s1: No such file or directory deenlo# mount -t msdosfs /dev/da2 /mnt/dos mount_msdosfs: /dev/da2: Invalid argument deenlo# mount -t msdosfs /dev/da2s1 /mnt/dos [success] So I'm guessing GEOM had to decide to create /dev/da2s1 after I tried to mount /dev/da2 directly? Nothing else would create the da2s1 device. Once the device was created with make_dev(), repeated unmounts/mounts work fine. -- Nate