From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 05:17:20 2005 Return-Path: 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 E869416A4CE for ; Tue, 5 Apr 2005 05:17:20 +0000 (GMT) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA66443D45 for ; Tue, 5 Apr 2005 05:17:20 +0000 (GMT) (envelope-from skip.ford@verizon.net) Received: from pool-70-104-70-104.pskn.east.verizon.net ([70.106.89.74]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IEG0077MK0M8NB4@vms044.mailsrvcs.net> for current@freebsd.org; Tue, 05 Apr 2005 00:17:11 -0500 (CDT) Date: Tue, 05 Apr 2005 01:17:16 -0400 From: Skip Ford In-reply-to: <20050404232917.I5371@odysseus.silby.com> To: Mike Silbersack Message-id: <20050405051716.GA654@pool-70-104-70-104.pskn.east.verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <20050404232917.I5371@odysseus.silby.com> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: msdosfs or ehci corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 05 Apr 2005 05:17:21 -0000 Mike Silbersack wrote: > I just ran into a problem on my laptop with a March 30th build of current, > using ehci. I tried mving a bunch of files and directories to my usb > thumb drive (which is using msdosfs), and mv returned a few errors about > files with that name already existing. I ran into an odd situation with msdosfs as well within the last few days which sounds related. While playing tunes from an msdosfs, some files played the wrong song. Mplayer indicates it's playing one song, while another one comes out the speakers. It's as though mplayer tries to open one file, but another gets opened instead. When attempting to play ~60 files in an msdos directory, for ~10 of them the music didn't match the filename mplayer indicated it was playing. The same doesn't happen for files in UFS directories. Perhaps in your case, the same thing is happening to mv(1). My last kernel, dated Feb 14, didn't exhibit this behavior. My current kernel is from Apr 2. I didn't install any in the middle of that range. -- Skip