[OpenAFS] renaming a volume caused headache

Christof Hanke hanke@rzg.mpg.de
Thu, 02 Aug 2007 14:02:29 +0300

Helmut Jarausch wrote:
> On  2 Aug, Russ Allbery wrote:
>> Helmut Jarausch <jarausch@igpm.rwth-aachen.de> writes:
>>> one of my collegues has married and therefore changed his name.
>>> I had a volume called - say Miller - and a directory ABC on that volume.
>>> I have renamed the volume 'Miller' to 'Smith', but now I cannot
>>> access the directory 'ABC' anymore.
>>> What can I do about this?
>> Run fs checkv on the system that's having trouble.
>> Volume renamings can sometimes cause odd artifacts like this because the
>> name to ID mappings get out of date on the client and the client doesn't
>> recheck them immediately.
> Thanks, but unfortunately this doesn't help.
> fs checkv
> All volumeID/name mappings checked.
> pushd /afs/.../home
> file Smith
> Smith directory
> cd Smith
> -bash: cd: Smith: No such device

What does "fs lsm Smith" say ?
Is it still the old volume-name ?

You might try to flush the client cache using "fs flushmount" or "fs 
flushvol /afs/.../home"