From owner-freebsd-hackers Mon Jun 19 07:34:19 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA20272 for hackers-outgoing; Mon, 19 Jun 1995 07:34:19 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA20251 for ; Mon, 19 Jun 1995 07:34:16 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id HAA05383; Mon, 19 Jun 1995 07:34:14 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id HAA02241; Mon, 19 Jun 1995 07:34:33 -0700 Message-Id: <199506191434.HAA02241@corbin.Root.COM> To: Robert Withrow cc: hackers@freebsd.org Subject: Re: Update: 2.0.5 scrambled filesystems. In-reply-to: Your message of "Mon, 19 Jun 95 10:15:07 EDT." <199506191415.KAA04039@rwwa.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 19 Jun 1995 07:34:33 -0700 Sender: hackers-owner@freebsd.org Precedence: bulk >> Yeah, try not mounting your dos filesystem and see if that makes any >> difference. > >Bingo! What gives? How does reading from the /dos filesystem clobber >the /usr filesystem? Does this bug show up on all systems? Shouldn't >this be flagged in red in the installation >info? Um, well, if we knew it was *that* broken, I suppose. I don't really know why it is clobbering things, but a quick guess would be that it is using old vnodes that have been reclaimed...but I really have no idea. We've known that msdosfs is broken for sometime - but not in this particular way. "Oh well". :-) -DG