From owner-freebsd-current Sat Sep 2 16:24:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA10771 for current-outgoing; Sat, 2 Sep 1995 16:24:30 -0700 Received: from mpp.minn.net (mpp.Minn.Net [204.157.201.242]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA10765 for ; Sat, 2 Sep 1995 16:24:28 -0700 Received: (from mpp@localhost) by mpp.minn.net (8.6.11/8.6.9) id SAA01333; Sat, 2 Sep 1995 18:24:09 -0500 From: Mike Pritchard Message-Id: <199509022324.SAA01333@mpp.minn.net> Subject: Re: Superblocks getting trashed with -current To: bde@zeta.org.au (Bruce Evans) Date: Sat, 2 Sep 1995 18:24:08 -0500 (CDT) Cc: bde@zeta.org.au, freebsd-current@freebsd.org In-Reply-To: <199509022318.JAA16564@godzilla.zeta.org.au> from "Bruce Evans" at Sep 3, 95 09:18:38 am X-Mailer: ELM [version 2.4 PL24 ME7a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 845 Sender: current-owner@freebsd.org Precedence: bulk Bruce Evans wrote: > > >I've had r/w mounted msdos file systems for something like 6 months > >without seeing these problems, so I don't think that is it. > >Or did someone break msdosfs stuff sometime in early August? > >And at least with todays problem, I wasn't accessing the > >msdos file systems at all. > > Probably not in early August. msdosfs has some unexplained disk > trashing problems from before that. Does the problem go away when msdos file system are mounted read-only? If so, I'll go mount them all that way (or maybe just not mount them at all) and see if the problem shows up again. Both times it happened, I had only been running the -current kernel for less than an hour, so it seems somewhat easy to reproduce. -- Mike Pritchard mpp@mpp.minn.net "Go that way. Really fast. If something gets in your way, turn"