[OpenAFS] Re: reading files from problem volume

[Andrew Deason]

On Thu, 22 Aug 2013 16:10:41 -0500
Andrew Deason <adeason@sinenomine.net> wrote:

> On Thu, 22 Aug 2013 14:24:41 +0000
> "sabah s. salih" <sabah.salih@hep.manchester.ac.uk> wrote:
>
> > 08/22/2013 09:04:07 Found 0 link count file /vicepcc/AFSIDat/Z=/Zh++U/M/02/zzzzPci=++0.
> > 08/22/2013 09:04:30 Found 0 link count file /vicepcc/AFSIDat/Z=/Zh++U/f/z3/zzzzPIq0++0.
> > 08/22/2013 09:04:31 2 nVolumesInInodeFile 64
> > 08/22/2013 09:04:31 CHECKING CLONED VOLUME 536872682.
> > Unable to open inode (Volume information) of volume header (error = 2)
> 
> That is not supposed to happen; this looks like a bug.

All of that more complicated stuff I said wasn't really necessary; I
missed the obvious paths listed above. You should try moving this file:

/vicepcc/AFSIDat/Z=/Zh++U/f/z3/zzzzPIq0++0

to the directory /vicepcc/AFSIDat/Z=/Zh++U/special/. If that directory
already has a file called zzzzPIq0++0, then just delete
/vicepcc/AFSIDat/Z=/Zh++U/f/z3/zzzzPIq0++0 (or move it somewhere outside
of /vicepcc).

You should also delete this file:

/vicepcc/AFSIDat/Z=/Zh++U/M/02/zzzzPci=++0

or just move it somewhere outside of /vicepcc. That file (zzzzPci=++0)
is a metadata file for the volume 536872682, but it's in the wrong place
on disk. If volume 536872682 does not appear to be a volume that's
actually in use, you can probably just get rid of it. (Try looking for
it with 'vos listvl 536872682').

Do you have any idea how those files could have gotten out of place? I'm
not sure how they could have gotten there by OpenAFS processes alone.

-- 
Andrew Deason
adeason@sinenomine.net