From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 07:13:10 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 18E8516A4CE for ; Tue, 5 Apr 2005 07:13:10 +0000 (GMT) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id E49A643D31 for ; Tue, 5 Apr 2005 07:13:09 +0000 (GMT) (envelope-from skip.ford@verizon.net) Received: from pool-70-104-70-104.pskn.east.verizon.net ([70.106.89.74]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IEG00C7HPDV1JL3@vms048.mailsrvcs.net> for current@freebsd.org; Tue, 05 Apr 2005 02:13:09 -0500 (CDT) Date: Tue, 05 Apr 2005 03:13:13 -0400 From: Skip Ford In-reply-to: <20050405011655.E5383@odysseus.silby.com> To: Mike Silbersack Message-id: <20050405071313.GA681@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> <20050405051716.GA654@pool-70-104-70-104.pskn.east.verizon.net> <20050405011655.E5383@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 07:13:10 -0000 Mike Silbersack wrote: > On Tue, 5 Apr 2005, Skip Ford wrote: > > >I ran into an odd situation with msdosfs as well within the last > >few days which sounds related. > > I'm not crazy! Whoo! I thought it was me! My eyes were reading one song title and my ears were hearing a completely different song... > Is yours on a USB connected drive, or a drive connected via ata/scsi? If > yours is ata/scsi, then we can eliminate USB from the problem. Mine's ata. I did a little more testing. In my case, the same files are always affected. Those files do appear identical, other than the names. They're the same size and there's no difference in contents. However, the affected files can swap contents. IOW, two files with different names will have the same contents which match one of the two original files, but then both files will switch contents to the other original file's contents. So, there doesn't appear to be any on-disk corruption. The contents of both original files are still there. -- Skip