From owner-freebsd-hackers Tue Jan 9 11:40:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA00892 for hackers-outgoing; Tue, 9 Jan 1996 11:40:18 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA00887 for ; Tue, 9 Jan 1996 11:40:15 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA12588; Tue, 9 Jan 1996 12:31:18 -0700 From: Terry Lambert Message-Id: <199601091931.MAA12588@phaeton.artisoft.com> Subject: Re: DOS File system fixes To: dfr@render.com (Doug Rabson) Date: Tue, 9 Jan 1996 12:31:18 -0700 (MST) Cc: bde@zeta.org.au, joerg_wunsch@uriah.heep.sax.de, terry@lambert.org, freebsd-hackers@FreeBSD.org, root@synthcom.com In-Reply-To: from "Doug Rabson" at Jan 9, 96 03:38:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > > >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? I am quoting behaviour/bug reports from the -questions list following the 2.1 release when I report the *apparent* problem. Note the use of the word "apparent"... it means I think the problem descriptions are analogous. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.