Date: Thu, 12 Oct 1995 14:58:26 -0700 From: Scott Blachowicz <scott@statsci.com> To: "Justin T. Gibbs" <gibbs@freefall.FreeBSD.org> Cc: "Dima (ELO)" <dima@escape.com>, questions@freebsd.org, support@freebsd.org Subject: Re: problem Message-ID: <m0t3Ve1-000r3xC@main.statsci.com> In-Reply-To: Your message of "Thu, 12 Oct 1995 14:17:04 -0700." <199510122117.OAA03809@aslan.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Justin T. Gibbs" <gibbs@freefall.FreeBSD.org> wrote:
> Our msdosfs is broken for filesystems > ~500MB in my experience. Its
> just another thing that needs to be fixed in msdosfs.
And in my experience (read: one system), it is broken, period. Are you talking
of _disks_ > ~500Mb or _filesystems_? When I messed with msdosfs on my system
(a 1Gb IDE disk & a 1.4Gb SCSI disk on a 2.0.5R installed from CD) I ended up
getting corrupted BSD partitions for my trouble - even when I only mounted the
msdos slices read-only. And I don't have any slices or filesystems that are
that big.
The system works great now that I don't get anywhere near the msdos slices. I
CAN just use the mtools package to get at my msdos disks anyways - not as
convenient, but it does seem to work.
I would LOVE to hear that things have been fixed up in later releases...I might
even try it once I get good backups and a recovery plan thought out...
Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc.
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0t3Ve1-000r3xC>