From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 13:50:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BEF310657C1 for ; Wed, 4 Nov 2009 13:50:25 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id DAD808FC26 for ; Wed, 4 Nov 2009 13:50:24 +0000 (UTC) Received: from mobileKamikaze.norad (vpn-cl-163-243.rz.uni-karlsruhe.de [141.3.163.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id D06848A0DC6; Wed, 4 Nov 2009 14:50:22 +0100 (CET) Message-ID: <4AF1869D.6090304@bsdforen.de> Date: Wed, 04 Nov 2009 14:50:21 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.23 (X11/20091024) MIME-Version: 1.0 To: Alexander Best References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Mark Linimon , freebsd-current@freebsd.org, Paul G Webster Subject: Re: 8.0-RC2 mangles msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 04 Nov 2009 13:50:25 -0000 Alexander Best wrote: > Paul G Webster schrieb am 2009-11-03: > *lol* just tried this myself and my fdisk output looks just as bad as yours: I think funny fdisk output is not that much of a problem. I normally put a single file system on external drives and don't bother partitioning. This is also a common default for many portable audio players. Heavy file system corruption with every write operation really renders msdosfs completely unusable. Now, I've got to rip my CDs and DVDs under FreeBSD and reboot into Windows to copy music and videos onto my player. This is really annoying for such a trivial use case. And msdosfs is still the default file system for portable devices, so it's an important desktop use case. Even in the business world, where often restrictive networks render USB sticks the only acceptable method of transporting large chunks of data. What I wonder is - are there more people who witness file system corruption upon msdosfs writes (and don't forget that either newfs_msdos or fsck_msdosfs is broken as well, and that fsck_msdosfs certainly does not recognize cross-linked files). The impact is so horrid that I had to reformat my portable player (with Windows) and reinstall the firmware to get it back going. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?