From owner-freebsd-hackers Tue Jan 9 07:47:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA16796 for hackers-outgoing; Tue, 9 Jan 1996 07:47:12 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA16760 for ; Tue, 9 Jan 1996 07:45:58 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id PAA26235; Tue, 9 Jan 1996 15:38:08 GMT Date: Tue, 9 Jan 1996 15:38:07 +0000 (GMT) From: Doug Rabson To: Bruce Evans cc: joerg_wunsch@uriah.heep.sax.de, terry@lambert.org, freebsd-hackers@FreeBSD.org, root@synthcom.com Subject: Re: DOS File system fixes In-Reply-To: <199601091140.WAA18562@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org Precedence: bulk On Tue, 9 Jan 1996, Bruce Evans wrote: > >> 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. I vaguely remember the reports of this kind of corruption being 'pre slice' era but I could be mistaken. Can anyone remember? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939