From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 04:33:40 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 E2D4616A4CE for ; Tue, 5 Apr 2005 04:33:40 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 5517643D39 for ; Tue, 5 Apr 2005 04:33:40 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 68867 invoked from network); 5 Apr 2005 04:33:39 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 5 Apr 2005 04:33:39 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 4 Apr 2005 23:33:35 -0500 (CDT) From: Mike Silbersack To: current@freebsd.org Message-ID: <20050404232917.I5371@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 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 04:33:41 -0000 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 went to look, and a few directories had been created _as files_, with contents from similar files! I tried a manual mkdir, and the same thing happened. I unmounted, and windows chkdsk found crosslinked files in that directory, which it was able to repair... but I'm going to have to doublecheck and see what got corrupted. So, here's the question: Since the directory I was copying all these files into was created right before the mv was started, does this mean that FreeBSD somehow created the crosslinked files/directories, or is it possible that a crosslink pre-existed, which caused something to go weird? Any other possibilities? Is this something that might have been fixed since the 30th somehow? Thanks, Mike "Silby" Silbersack