Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Dec 1995 12:37:11 -0700 (MST)
From:      Terry Lambert <terry@lambert.org>
To:        scott@statsci.com
Cc:        terry@lambert.org, tb@MO.NET, questions@freebsd.org
Subject:   Re: Filesystems corrupted - what's up with this?
Message-ID:  <199512081937.MAA01962@phaeton.artisoft.com>
In-Reply-To: <199512072242.OAA07046@block.statsci.com> from "Scott Blachowicz" at Dec 7, 95 02:42:28 pm

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> > Are you using msdos FS in read/write mode?
> 
> Sounds like what I get when I mount an msdosfs in ANY mode (read/write OR
> read-only) on my 2.0.5-RELEASE system (I haven't been brave enough to try
> it ont the 2.1.0-mumble-SNAP system I have access to).  It seemed to be
> related, somehow, to having used FIPS to shrink my DOS partitions to make
> room for a real OS.  From discussions I've seen, it seems to be a problem
> in the FreeBSD msdosfs (as opposed to FIPS) - mounting the DOS partitions
> seems to work just dandy from DOS/Windows, Windows NT and Linux.

Well, DOS/Windows and Windows NT don't have real caches when using the
FAT FS.  Linux has 1k blocks on reading.

It really does look to be FIPS related, which is an important clue,
since the FAT size dictates the writable disk area.

I'm betting that your FAT FS is before your BSD FS on the same disk?

Like I said in another message, I will rewrite this at some time in
the future if someone else doesn't get to it first.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?199512081937.MAA01962>