From owner-freebsd-hackers  Mon Jun 19 07:56:47 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id HAA22427
          for hackers-outgoing; Mon, 19 Jun 1995 07:56:47 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA22420
          for <hackers@freebsd.org>; Mon, 19 Jun 1995 07:56:40 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA06908; Tue, 20 Jun 1995 00:49:49 +1000
Date: Tue, 20 Jun 1995 00:49:49 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506191449.AAA06908@godzilla.zeta.org.au>
To: davidg@root.com, witr@rwwa.com
Subject: Re: Update: 2.0.5 scrambled filesystems.
Cc: hackers@freebsd.org
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

Next try mounting it read-only.

If there is a bug in msdosfs, then it might corrupt the buffer or vnode
cache.  Then reading of other (POSIX) file systems would probably corrupt
them when the access time stomps are updated even if you don't do any
explicit writes.  msdosfs doesn't have access time fields so it wouldn't
be affected.

>the /usr filesystem?  Does this bug show up on all systems?  Shouldn't

Of course not.

>this be flagged in <bold><italic>red  </italic></bold>in the installation 
>info<bold><italic>?</italic></bold>

Yes.

Bruce