Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!eye!paul
From: paul@eye.com (Paul B. Booth)
Newsgroups: comp.sys.apollo
Subject: disk data check on DN10K
Message-ID: <1991Jan25.171209.3703@eye.com>
Date: 25 Jan 91 17:12:09 GMT
Reply-To: paul@eye.com (Paul B. Booth)
Organization: 3D/Eye Inc., Ithaca, NY
Lines: 19

Hi all.  We've recently been trying to run some LARGE ray-traces on our DN10k.  
Most of these are batch jobs that write out large numbers of images in
sequence, and we tend to run 4 such jobs at a time (1 job/cpu).  What's been
happening though, is that these jobs will bomb out after some random number of
frames are generated with the error: "disk data check."  Re-running the job
may work, or it may bomb out after a differrnt number of frames.  Any clue as
to what this means?  Someone here thought that it might be due to bad spots
on the disk.  Any ideas how I might determine this?  My (limited) understanding
of invol tells me that invol will print out the factory-written badspot list
of a disk and allow me to add to that list, but I don't know how to find
bad-spots that might have developed since the disk was shipped from the
factory.  I've run salvol to no avail, and am basically w/o clue at this point.

Thanks in advance for any help!
--
Paul B. Booth  (paul@eye.com) (...!hplabs!hpfcla!eye!paul)
-------------------------------------------------------------------------------
3D/EYE, Inc., 2359 N. Triphammer Rd., Ithaca, NY  14850    voice: (607)257-1381
                                                             fax: (607)257-7335