From owner-freebsd-hackers  Sun Jun 18 19:01:12 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA16000
          for hackers-outgoing; Sun, 18 Jun 1995 19:01:12 -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 TAA15994
          for <hackers@freebsd.org>; Sun, 18 Jun 1995 19:01:09 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id TAA04865; Sun, 18 Jun 1995 19:01:08 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA00928; Sun, 18 Jun 1995 19:01:26 -0700
Message-Id: <199506190201.TAA00928@corbin.Root.COM>
To: Robert Withrow <witr@rwwa.com>
cc: hackers@freebsd.org
Subject: Re: Update: 2.0.5 scrambled filesystems. 
In-reply-to: Your message of "Sun, 18 Jun 95 21:44:05 EDT."
             <199506190144.VAA02970@rwwa.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sun, 18 Jun 1995 19:01:25 -0700
Sender: hackers-owner@freebsd.org
Precedence: bulk

>Problem: scrambled filesystems result from doing:
>``find / -type f -print | xargs cat >/dev/null''
>
>I've tried several things (listed shortly) and keep getting the
>same basic problem (either panics due to scrambled filesystems,
>or the command completes, but a following ``fsck -n'' shows all
>kinds of corruption.  The curruption is still there after a re-boot.
>Often the system isn't able to sync out the final disk blocks (it
>says ``giving up''.  The fsck errors seen are always on either
>the /dos filesystem, the /usr filesystem, or both, but *never*
>on the / (root) filesystem.  Also, booting on dos and running
>scandisk never shows any problems (and running some of the dos
>software whose file are mentioned on the fsck output is ok too).
...
>Ideas?


   Yeah, try not mounting your dos filesystem and see if that makes any
difference.

-DG