From owner-freebsd-hackers Tue Jan 9 03:55:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA04086 for hackers-outgoing; Tue, 9 Jan 1996 03:55:58 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA04064 for ; Tue, 9 Jan 1996 03:55:45 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA18562; Tue, 9 Jan 1996 22:40:19 +1100 Date: Tue, 9 Jan 1996 22:40:19 +1100 From: Bruce Evans Message-Id: <199601091140.WAA18562@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, terry@lambert.org Subject: Re: DOS File system fixes Cc: freebsd-hackers@FreeBSD.org, root@synthcom.com Sender: owner-hackers@FreeBSD.org Precedence: bulk >> There are several reports that enabling DOS f/s read/write can damage >> other file systems. I haven't seen such a report for a long time, or such report with enough details (not even from me after I saw the problem :-) >It seems that if you use FIPS or PRESIZE or "Partition Magic" to resize >your partition, the cluster size will not be reduced. >This results in crap being written out to the "phantom" locations as if >it were a bigger disk. This should only affect the slice containing the DOS file system. The device number would have to be corrupted for a write to affect another device. >There is some indication that mark-for-update occurs on read-only devices, >and that for MSDOSFS, this update actually takes place. I think this was fixed a long time ago. Bruce