Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!umich!terminator!dabo.ifs.umich.edu!rees
From: rees@dabo.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Bad blocks on DN10000 disk: crash: which files affected?
Keywords: bad disk blocks DN10000 lsyserr salvol dex invol
Message-ID: <1990Jul19.015827.8312@terminator.cc.umich.edu>
Date: 19 Jul 90 01:58:27 GMT
References: <1990Jul18.043746.712@metro.ucc.su.OZ.AU>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 16

In article <1990Jul18.043746.712@metro.ucc.su.OZ.AU>,
szabo_p@maths.su.oz.au (Paul Szabo) writes:
  The question is: Is there a way of finding out what file is stored at
  that place on the disk?

Someone else already mentioned rwvol.  Another useful little program is
fixvol.  Use both with extreme caution.

  Note that there seems to be a discrepancy between the address 21174
  reported by SALVOL, and the address 21176 reported by lsyserr (this is
  the closest I could find).

Salvol is reporting an lvol daddr, and lsyserr is reporting a physical
daddr.  There is some cruft on the volume before the start of the lvol,
accounting for the difference here (although I'm not sure why it's 2 and not
1).