From owner-freebsd-hackers  Sun Jun 18 13:36:45 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA02300
          for hackers-outgoing; Sun, 18 Jun 1995 13:36:45 -0700
Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02290
          for <hackers@freebsd.org>; Sun, 18 Jun 1995 13:36:39 -0700
Received: by haven.uniserve.com id <30751>; Sun, 18 Jun 1995 13:37:36 +0100
Date: 	Sun, 18 Jun 1995 13:37:25 -0700 (PDT)
From: Tom Samplonius <tom@uniserve.com>
To: Robert Withrow <witr@rwwa.com>
cc: hackers@freebsd.org
Subject: Re: 2.0.5R -- Filesystems getting scrambled...
In-Reply-To: <199506181316.JAA01366@rwwa.com>
Message-ID: <Pine.BSF.3.91.950618133207.4912H-100000@haven.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@freebsd.org
Precedence: bulk


On Sun, 18 Jun 1995, Robert Withrow wrote:

> Doing a ``find / -type f -print | xargs cat >/dev/null'' causes a panic
> because of scrambled filesystems.
> 
> 2.0.5R, Pentium 75Mhz, ``Sis'' [?] chipset, 24 MB memory, onboard ide,
> WD caviar 1.22G drive.

  Not on every system.  On a 486SLC 2/66 with a cyrix mathco, 4 megs 
of RAM, local bus EIDE and a Maxtor 540Meg drive runing 2.0.5R, it completed 
flawlessly.

> This is obviously a showstopper problem for me, since I have no way of
> knowing what specific feature of the above pipeline is causing the
> scrambling, and so I have no way of knowing if some other innocent
> software or bumbling user will also scramble my file systems...

  Nothing in that pipeline should even modify the filesystem. 

  Check RAM, cache, and cache settings.

Tom