From owner-freebsd-current Thu Apr 4 15:36:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA16509 for current-outgoing; Thu, 4 Apr 1996 15:36:48 -0800 (PST) Received: from eac.iafrica.com (slipper101139.iafrica.com [196.7.101.139]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16459 for ; Thu, 4 Apr 1996 15:36:23 -0800 (PST) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id BAA00779 for current@freebsd.org; Fri, 5 Apr 1996 01:30:05 +0200 From: Robert Nordier Message-Id: <199604042330.BAA00779@eac.iafrica.com> Subject: Re: 2.2-960323 Panic in mount_msdos To: current@freebsd.org Date: Fri, 5 Apr 1996 01:30:04 +0200 (SAT) In-Reply-To: <199604042010.NAA22425@phaeton.artisoft.com> from "Terry Lambert" at Apr 4, 96 01:10:04 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Apr 1996, Terry Lambert wrote: > The fix for inconsistent media is to run fsck (or equivalent) on it > before attempting a mount; the fix is procedural, in other words, > and doesn't require a change to the mount code. > > The DOSFS code is, unfortunately, well known to be unstable. It > does not do the type validation it should, ad there is not a fsck > equivalent program as part of the package. > > The DOSFS is being rewritten (not by me). > > For now, make sure that you have chkdsk'ed the DOS disk prior to > booting FreeBSD. If it fails chkdsk, do not attempt to mount it. A dosfsck has been created as part of the rewrite of the msdosfs, and should be ready for beta testing in a few weeks. -- Robert Nordier