I have a number of temp volumes that I'm trying to delete but having
problems within our AFS filesystem. Does anyone have a suggestion on how
to diagnose the 'Possible communication failure' error? I'm not finding
anything on google. Here is an example of a volume that I try to remove
but it won't go totally away.
bash-3.2# vos remove -server velma.psc.edu -partition /vicepcd -id
tmp.users.9.zzhao3 -localauth
WARNING: Volume 537606306 does not exist in VLDB on server and partition
Volume 537606306 on partition /vicepcd server velma.psc.edu deleted
bash-3.2# vos volinfo -id tmp.users.9.zzhao3 -localauth
Could not fetch the information about volume 537606306 from the server
Possible communication failure
Error in vos examine command.
Possible communication failure
Dump only information from VLDB
tmp.users.9.zzhao3
RWrite: 537606306
number of sites -> 1
server velma.pvt.psc.edu partition /vicepcd RW Site
bash-3.2# vos syncvldb -server velma.psc.edu -partition vicepcd -volume
tmp.users.9.zzhao3 -dryrun -localauth -verbose
Processing VLDB entry tmp.users.9.zzhao3 ...
_______________________________
-- status before --
tmp.users.9.zzhao3
RWrite: 537606306
number of sites -> 1
server velma.pvt.psc.edu partition /vicepcd RW Site
Transaction call failed for RW volume 537606306 on server velma.pvt.psc.edu
/vicepcd
Could not process VLDB entry for volume tmp.users.9.zzhao3
Possible communication failure
Error in vos syncvldb command.
Possible communication failure
...error encounteredbash-3.2# vos examine -volume tmp.users.9.zzhao3
vos: Unrecognized or ambiguous switch '-volume'; type 'vos help examine'
for detailed help
bash-3.2# vos examine tmp.users.9.zzhao3
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
bash-3.2# vos examine tmp.users.9.zzhao3 -localauth
Could not fetch the information about volume 537606306 from the server
Possible communication failure
Error in vos examine command.
Possible communication failure
Dump only information from VLDB
tmp.users.9.zzhao3
RWrite: 537606306
number of sites -> 1
server velma.pvt.psc.edu partition /vicepcd RW Site
bash-3.2# vos unlockvldb tmp.users.9.zzhao3
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
vos: server 'tmp.users.9.zzhao3' not found in host table
bash-3.2# vos unlockvldb -server velma.psc.edu -partition vicepcd -volume
tmp.users.9.zzhao3 -localauth
vos: Unrecognized or ambiguous switch '-volume'; type 'vos help unlockvldb'
for detailed help
bash-3.2# vos unlock tmp.users.9.zzhao3
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
Could not unlock the entry for volume number 537606306 in VLDB
VLDB: no permission access for call
Error in vos unlock command.
VLDB: no permission access for call
bash-3.2# vos unlock tmp.users.9.zzhao3 -localauth
Released lock on vldb entry for volume tmp.users.9.zzhao3
bash-3.2# vos examine tmp.users.9.zzhao3 -localauth
Could not fetch the information about volume 537606306 from the server
Possible communication failure
Error in vos examine command.
Possible communication failure
Dump only information from VLDB
tmp.users.9.zzhao3
RWrite: 537606306
number of sites -> 1
server velma.pvt.psc.edu partition /vicepcd RW Site
bash-3.2# vos syncvldb -server velma.psc.edu -partition vicepcd -volume
tmp.users.9.zzhao3 -dryrun -localauth -verbose
Processing VLDB entry tmp.users.9.zzhao3 ...
_______________________________
-- status before --
tmp.users.9.zzhao3
RWrite: 537606306
number of sites -> 1
server velma.pvt.psc.edu partition /vicepcd RW Site
Transaction call failed for RW volume 537606306 on server velma.pvt.psc.edu
/vicepcd
Could not process VLDB entry for volume tmp.users.9.zzhao3
Possible communication failure
Error in vos syncvldb command.
Possible communication failure
