Date: Thu, 28 Nov 1996 13:07:34 +0200 (SAT) From: Robert Nordier <rnordier@iafrica.com> To: j@uriah.heep.sax.de (J Wunsch) Cc: freebsd-hackers@freebsd.org, rnordier@iafrica.com Subject: Re: A simple way to crash your system. Message-ID: <199611281107.NAA00867@eac.iafrica.com> In-Reply-To: <199611280947.KAA01216@uriah.heep.sax.de> from J Wunsch at "Nov 28, 96 10:47:56 am"
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch wrote: > As Robert Nordier wrote: > > > By default, msdosfs would in future not mount DOS FSes with a block > > size exceeding 32 (or maybe 16) sectors, since these appear to be > > the filesystems that trigger the UFS corruption problem. > > > > However, to revert to present behavior (ie. mount any DOS partition), > > either: > > > > (a) Use mount(8) or mount_msdos(8) with the -f (force) option; or > > (b) Specify MSDOSFS_FORCE as a kernel configuration option. > > Assuming it's documented in LINT, GENERIC, and mount_msdos(8), i think > this is a fine compromise. I see John Dyson has committed a change to trap FS buffer requests larger than the vfs layer is set up to handle, and increased MAXBSIZE (where MSDOSFS is defined) to 32768. Anyone know if John's change does anything to eliminate the `MSDOSFS corrupts UFS' problem? (I've never been able to reproduce it here.) If the change doesn't eliminate the corruption, the problem may not be directly related to MAXBSIZE. In which case, restricting the MSDOSFS to supporting only DOS 3.30 (less than 32MB) partitions (unless "forced") may be the logical and/or safest step. -- Robert Nordier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611281107.NAA00867>