From owner-freebsd-questions Mon Oct 14 15:35:39 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01641 for questions-outgoing; Mon, 14 Oct 1996 15:35:39 -0700 (PDT) Received: from freenet.hamilton.on.ca (main.freenet.hamilton.on.ca [199.212.94.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA01602 for ; Mon, 14 Oct 1996 15:35:13 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id SAA05797; Mon, 14 Oct 1996 18:33:55 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id SAA29381; Mon, 14 Oct 1996 18:35:45 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Mon, 14 Oct 1996 18:35:44 -0400 (EDT) From: Tim Vanderhoek Reply-To: Tim Vanderhoek To: Sergios cc: questions@freebsd.org Subject: Re: msdosfs broken... In-Reply-To: <2.2.32.19961014212539.009af974@prometheus.hol.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Oct 1996, Sergios wrote: > Just of curiosity what exactly happens in this case? Once I mounted a large > dos partition to copy some files there and on boot the bsd / had vanished > [!]. I had to reinstall / but I am still curious why it was the / filesystem > that got corrupted and not the dos partition.... Yours vanished? Hmm... Consider yourself lucky... Mine didn't quite go away so I ended up spending much time trying to save what turned out to be pretty much unsaveable... > (Now I have / in its own slice and differrent partitions for /usr /var etc. > so In Case Shi* happens I will not have to reinstall everything.) I didn't try mounting the root dir on a slice especially for it, but I do know that having different partitions for /usr, etc. won't protect you from the msdosfs code. You probably would've lost your bsd slice to msdosfs even if you hadn't tried copying files to/from dos/. Just a simple `ls /dos' would do the trick. >From the fact that you don't even have to make msdosfs write to the hdd, I'd guess that it doesn't actually ruin the bsd slice itself, but somehow convinces ufs to do it. hehe... I tried mounting `/' as readonly to prevent that, then quickly found I couldn't boot with '/' as readonly, and that to change '/' from readonly, one has to write to `/'... The odd thing, if I remember correctly, is that it does actually seem to read the DOS slice correctly and whatsmore, doesn't damage the DOS slice at all (or visibly, at least). The problem that you asked about, where msdosfs complains about the cluster size not being right, causes a different problem, namely corruption of the DOS slice (not the BSD slice). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk