Date: Thu, 09 Aug 2007 15:43:59 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Philipp Mergenthaler <philipp.mergenthaler@stud.uni-karlsruhe.de> Cc: current@freebsd.org, bde@freebsd.org Subject: Re: Data corruption with msdosfs (rev. 1.172 of msdosfs_vnops.c) Message-ID: <20070809154359.fre23qndsk8ockc4@webmail.leidinger.net> In-Reply-To: <20070804142854.GA24178@rzstud5.rz.uni-karlsruhe.de> References: <20070804142854.GA24178@rzstud5.rz.uni-karlsruhe.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Philipp Mergenthaler =20 <philipp.mergenthaler@stud.uni-karlsruhe.de> (from Sat, 4 Aug 2007 =20 16:28:54 +0200): > > Hi, > > with rev. 1.172 of msdosfs_vnops.c I see data corruption when reading file= s > on a FAT 32 file system. (I didn't try write accesses apart from deleting > some files, which worked ok). The file system is on a IDE disk in an > external USB enclosure and has been created with "newfs_msdos -F 32", IIRC= . > I can use it without problems under FreeBSD-current (prior to July 20th), > Windows XP and Linux. I asked bde (the last one who touched the msdosfs) if he has seen your =20 report. As he doesn't read -current, he hasn't. Here's his response =20 (please keep him in CC): ---snip--- I haven't seen that problem here. There is the easy workaround of mounting with -noclusterr (except I think -noclusterr is not honored by mmap, oops). Ask the OP if this works even with mmap (mmap can be tested using cp), and what all the fs parameters are (newfs_msdos prints them. Was -F 32 the onlt parameter used? That parameter has no effect since it is the default for non-small filesystems). ---snip--- Bye, Alexander. --=20 BOFH excuse #278: The Dilithium Crystals need to be rotated http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070809154359.fre23qndsk8ockc4>