[153] in Info-AFS_Redistribution
Re: Problems with backup volumes disappearing
daemon@ATHENA.MIT.EDU (Liz_Hines@transarc.com)
Mon Jun 17 19:43:45 1991
Date: Mon, 17 Jun 1991 19:24:34 -0400 (EDT)
From: Liz_Hines@transarc.com
To: bob@ibmpa.awdpa.ibm.com, Info-AFS@transarc.com,
Cc:
In-Reply-To: <9106150408.AA28201@antlia.ECE.CMU.EDU>
A couple of sites have complained about the fact that vos backupsys says
that it is cloning the volume, but it doesn't really and it doesn't give
an error message. Then it only gets noticed during backup.
First of all, vos backupsys should give an indication that not all clones
worked - this has been entered as a bug.
Secondly, VolserLog most likely indicates that there is a problem. In the
cases that I have seen, VolserLog contains an error of the form:
Volser: DumpVnode: dump: Unable to open inode xxxx for vnode yyyy; not dumped;
error 2
The backup system gives a message of the form:
vols: badly formatted dump
The solution to this problem is to salvage the volume and do a vos backup to
recreate the backup volume.
Please look at the VolserLog - this gives valuable information about volume
errors. If you see other errors, please pass that information on to us and
we will help you clean things up so backups can continue.
Liz Hines
Product Support Manager, File Systems
Transarc Corporation
