Date: Fri, 2 May 1997 18:36:32 -0500 (CDT) From: "Jay D. Nelson" <jdn@qiv.com> To: Robert Nordier <rnordier@iafrica.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Current status of msdosfs (yet again) Message-ID: <Pine.NEB.3.95.970502183214.391A-100000@acp.qiv.com> In-Reply-To: <199705022256.AAA15099@eac.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the response. In my blissful ignorance, I deleted some files and directories -- which didn't bother FreeBSD a bit. From what you're telling me, it's not wise to tar up the dos file system to restore after the format. Is there a gnuish version of tar... I'll grin and bear it. Thanks. -- Jay On Sat, 3 May 1997, Robert Nordier wrote: ->Jay Nelson wrote: -> ->> I have 2.2.1-RELEASE running at work and I'm being forced to soil myself ->> with Windows. I mounted dos from X, didn't see the messages and tried ->> moving some files. Everything worked fine. Is it safe to use msdosfs or ->> was I just lucky? -> ->The problem where the msdosfs corrupted other filesystems should not ->occur in any 2.2.x-RELEASE. -> ->> This is on a 1.6Gb IDE repartitioned with fips. Is there any way I can ->> control the cluster size if I reformat or will dos fdisk/format take care ->> of the problem? -> ->If you used FIPS, it is a good idea to reformat. Allow DOS format ->to choose the cluster size. (Having the default cluster size is ->always good: that way, if DOS/Win itself becomes confused, it won't ->chop your filesystem into small little pieces. :-) The 2.2 msdosfs ->is no longer "cluster size sensitive", though; so a reformat is not ->absolutely required. -> ->The msdosfs is reasonably safe for copying files DOS<->BSD. But ->stay away from anything much more than that (eg. moving directories ->can cause problems). -> ->-- ->Robert Nordier ->
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970502183214.391A-100000>