From owner-freebsd-current Sat Sep 2 15:55:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA10282 for current-outgoing; Sat, 2 Sep 1995 15:55:04 -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 PAA10275 for ; Sat, 2 Sep 1995 15:55:01 -0700 Received: (from mpp@localhost) by mpp.minn.net (8.6.11/8.6.9) id RAA01229; Sat, 2 Sep 1995 17:54:41 -0500 From: Mike Pritchard Message-Id: <199509022254.RAA01229@mpp.minn.net> Subject: Re: Superblocks getting trashed with -current To: bde@zeta.org.au (Bruce Evans) Date: Sat, 2 Sep 1995 17:54:40 -0500 (CDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199509022245.IAA15369@godzilla.zeta.org.au> from "Bruce Evans" at Sep 3, 95 08:45:39 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: 602 Sender: current-owner@freebsd.org Precedence: bulk Bruce Evans wrote: > > >I just saw a message in the past day or two from someone else that > >reported they had a trashed superblock. It looks like something > >in -current is eating them. > > Maybe msdosfs mounted r/w? 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. -- Mike Pritchard mpp@mpp.minn.net "Go that way. Really fast. If something gets in your way, turn"