From owner-freebsd-current@FreeBSD.ORG  Fri Jul 18 17:39:32 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BD4D537B401
	for <current@freebsd.org>; Fri, 18 Jul 2003 17:39:32 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4F3D943F75
	for <current@freebsd.org>; Fri, 18 Jul 2003 17:39:32 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 26890 invoked by uid 1000); 19 Jul 2003 00:39:33 -0000
Date: Fri, 18 Jul 2003 17:39:33 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Ian Dowse <iedowse@maths.tcd.ie>
In-Reply-To: <200307190012.aa48313@salmon.maths.tcd.ie>
Message-ID: <20030718173627.J26887@root.org>
References: <200307190012.aa48313@salmon.maths.tcd.ie>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: Problem with umount and fsid? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jul 2003 00:39:33 -0000

On Sat, 19 Jul 2003, Ian Dowse wrote:
> In message <20030718122134.B26395@root.org>, Nate Lawson writes:
> >I get an error when umounting a FAT filesystem on a USB flash drive.  It
> >appears the device is properly unmounted.  Is this a case that needs to be
> >fixed in our fsid code?  It happens every time I unmount this device.
>
> >laptop# umount /thumb
> >umount: unmount of /thumb failed: No such file or directory
> >umount: retrying using path instead of file system ID
> >laptop# mount | grep da0
> >laptop#
>
> Thanks for the report - in theory this should only occur if you
> have a kernel from before July 1st but a newer userland. Assuming
> that's not the case, I must have overlooked something. Could you
> update to the latest sbin/mount, and then post the output of:
>
> 	mount -v | grep /thumb
> 	truss umount /thumb

Will do but first I'll update my kernel to see if that fixes it.  It looks
like it was just under the wire:

FreeBSD laptop.example.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Mon Jun 30 03:09:24 PDT 2003  cvs@shoebox:/e/scratch/obj/e/data/FreeBSD/5-src/sys/LAPTOP  i386

Sorry for what looks like a false report.  I must have overlooked updating
my kernel due to the past boot problems gcc 3.3 caused.

-Nate