I was hoping these would go away at 3.3a. A volume fails to backup to tape, so I do the following: hannah> fs exa ~wickham Volume status for vid = 536872997 named home.jsethna.wickham Current disk quota is unlimited Current blocks used are 251294 The partition has 756548 blocks available out of 2048000 hannah> vos dump home.jsethna.wickham.backup -time 0 >/dev/null Error in rx_EndCall VOLSER: Problems encountered in reading the dump file ! Error in vos dump command hannah> vos remove ept a home.jsethna.wickham.backup Volume 536872999 on partition /vicepa server ept deleted hannah> vos backup home.jsethna.wickham Failed to clone the volume 536872997 Could not end transaction on the volume 536872997 Could not update the VLDB entry for the volume 536872997 Possible communication failure Error in vos backup command Additional data: This happens very infrequently. There have been no disk errors on the server. The same thing has happened to this same volume (and a few others on a different server) before. In the past, the most reliable method of fixing the problem has been to create another volume, 'tar | tar' the contents of the old volume to the new one, remove the old one, and rename the new one. This process recovers all data. Using 'salvage' instead has often resulted in loss of data, necessitating recovery from tape. This is getting a bit tiresome. -Rick -- |Rick Cochran 607-255-7223| |Cornell Materials Science Center [EMAIL PROTECTED]| |E20 Clark Hall, Ithaca, N.Y. 14853 cornell!msc.cornell.edu!rick| | "Workstations - I bet you can't eat just one!" |
