From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 22:10:23 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD5E616A4CE for ; Tue, 22 Mar 2005 22:10:23 +0000 (GMT) Received: from smtp818.mail.sc5.yahoo.com (smtp818.mail.sc5.yahoo.com [66.163.170.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E3A443D1F for ; Tue, 22 Mar 2005 22:10:23 +0000 (GMT) (envelope-from bmk0@pacbell.net) Received: from unknown (HELO ?192.168.0.2?) (bmk0@pacbell.net@67.174.233.252 with plain) by smtp818.mail.sc5.yahoo.com with SMTP; 22 Mar 2005 21:58:53 -0000 Message-ID: <4240951B.9010005@pacbell.net> Date: Tue, 22 Mar 2005 13:58:51 -0800 From: "Brian M. Kincaid" User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: emergent msdosfs problems, errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 22:10:24 -0000 Hello FreeBSD Collective Consciousness, I run a dual-boot FreeBSD 6.0-Current/WinXP Pro system. The FreeBSD NTFS driver can't write files, and can only read files less than 2GB in size, so I have been using a FAT32 disk (Drive D:) mounted using mount_msdosfs successfully for several years for file transfer between the FreeBSD and WinXP "personalities" of my system. Just recently, after some hardware changes in my machine (new SATA disks for the FreeBSD personality) and rebuilding of world and kernel, the MSDOS file system has become unreliable, with directories and files mixed up, and "find ." broken with various error messages. Also, fsck_msdosfs complains about bad signatures in the boot block. After a clean reboot, doing "find ." on the FAT32 disk works without errors. Running "tar" to try to create a backup of the FAT32 disk fails, though, and after that "find ." returns errors "find: fts_read: No such file or directory" and files and directories on the FAT32 disk appear to be mixed up or corrupted. In the WinXP world, the FAT32 disk is just fine, thank you. All this is new behavior, things have been working for several years. I think the FreeBSD msdosfs driver is failing somehow. Any suggestions? Thanks, Brian