[OpenAFS-devel] Error diagnosis - ReallyRead failure

Derrick J Brashear shadow@dementia.org
Tue, 12 Feb 2002 00:30:30 -0500 (EST)


On Mon, 11 Feb 2002, Neulinger, Nathan wrote:

> 
> Feb  8 09:48:04 afs8 fileserver[561]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> Feb  8 10:05:15 afs8 fileserver[562]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> Feb  8 10:15:50 afs8 fileserver[567]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> Feb  8 12:23:17 afs8 fileserver[555]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> Feb  8 12:40:19 afs8 fileserver[561]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> Feb  8 12:46:43 afs8 fileserver[560]: ReallyRead(): read failed device 2
> inode 80C1CC0 errno 5 
> 
> Any way to determine what volume that's on? I completely cleared one
> file server to another, and the failure followed with the same exact
> inode number, device changed though.
> 
> If that's a real inode - it's rather large, and disagrees with anything
> on disk, so I'm assuming that's an AFS inode.
> 
> It's 135,011,520 or 3,223,063,560 if LE.

http://www.mit.edu/afs/athena/contrib/watchmaker/src/afscalc/calcfid.c

note that it guesses about the volumeid, and sometimes is wrong because
there's isn't enough information to readily determine it.

-D