From owner-freebsd-questions Tue Oct 22 19:23:13 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA23416 for questions-outgoing; Tue, 22 Oct 1996 19:23:13 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA23404 for ; Tue, 22 Oct 1996 19:23:09 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id TAA06262; Tue, 22 Oct 1996 19:23:05 -0700 (PDT) Date: Tue, 22 Oct 1996 19:23:05 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Don Yuniskis cc: FreeBSD Questions Subject: Re: Making a DOS Partition writeable In-Reply-To: <199610220806.BAA21835@seagull.rtd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Ack! let's prune that cc: back to questions. On Tue, 22 Oct 1996, Don Yuniskis wrote: > > > > Please, anyone correct me, but mounting a DOS-FS could -- under certain > > > > circumstances -- corrupt the BSD-FS !?!? > > > > > > Shortly after I installed FreeBSD, I was running two finds on different > > > virtual consoles, with /msdos mounted, and my machine crashed hard. When > > > it came back up, my entire FreeBSD installation was hosed. I can't say it > > > was definitely due to msdosfs, but I suspect it. > > > > The primary problem comes when you FIPS a partition and cause the cluster > > size to change. FreeBSD assumes a perfect world while FIPS cheats -- it > > SHOULD rewrite all those sectors back down to the smaller clustersize but > > that takes a while (I had a program that actually did it right!) esp. on > > big disks. > > So, how does this result in the FBSD partition being trashed? Or, is that > an "ugly rumor"? Is it only applicable to a FBSD partition on the same > physical device as a FIPS'ed DOS partition? etc. I can't really say why it's corrupt the FreeBSD filesystem as well. My guess would be a wrong disklabel or partition table, but I can't say for sure. In any case bad things can happen. > It sure would be nice if these things were more thoroughly described or > qualified ... help reduce some of the "lore" surrounding them. The new msdosfs code should fix it once and for all. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major