From owner-freebsd-questions Thu Jan 18 01:27:34 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA13928 for questions-outgoing; Thu, 18 Jan 1996 01:27:34 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA13917 for ; Thu, 18 Jan 1996 01:27:30 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id BAA02957; Thu, 18 Jan 1996 01:25:18 -0800 From: Julian Elischer Message-Id: <199601180925.BAA02957@ref.tfs.com> Subject: Re: rel-2.1.0 and msdos file systems To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 18 Jan 1996 01:25:17 -0800 (PST) Cc: dan@westford.ccur.com, questions@FreeBSD.org In-Reply-To: <199601180858.TAA06169@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 18, 96 07:28:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@FreeBSD.org Precedence: bulk > > Dan Malek stands accused of saying: > > The problem I am having is with Release-2.1.0 and the MSDOS file > > system partition. Any modification to the 'C:' drive (/dev/wd0s1) > > corrupts my FreeBSD root partition (/dev/wd0s2a). The info: > ... > > I booted DOS 6.22 and ran FIPS to split up the drive: > > This is your problem; when FIPS shrunk your DOS drive, it reduced it such > that the cluster size would normally be reduced. This can't happen (for > obvious reasons), but the FreeBSD MSDOSFS code becomes confused by the > mismatch, and the corruption you're seeing is a result of this. You didn't notice the following part: "I have completely reformatted and reloaded MSDOS 6.22" he also states that no requests are being made to write beyond the new slice. the corruption is coming courtesy of the VFS code I think.. similarly, the other day my Dec-1 -current system scrambled all my device's major and minor numbers (!) and removed a lot of files. though it may have had something to do with a sick drive I had connected. >