[157] in Info-AFS_Redistribution
Re: Missing Backup Volumes
daemon@ATHENA.MIT.EDU (Bob Andrews)
Tue Jun 18 16:13:46 1991
From: bob@ibmpa.awdpa.ibm.com (Bob Andrews)
To: carrel@antlia.ece.cmu.edu (David Carrel)
Date: Tue, 18 Jun 91 10:54:21 PDT
Cc: Info-AFS@transarc.com, Liz_Hines@transarc.com
In-Reply-To: <9106181545.AA09607@antlia.ECE.CMU.EDU>; from "David Carrel" at Jun 18, 91 11:45 am
David Carrel writes:
> Date: Tue, 18 Jun 91 11:45:52 EDT
>
>
> I hate to contradict Liz's post, but we have been having this problem on the
> order of one volume a day turning up missing. We can salvage (volumes or
> partitions) till we are blue in the face to no avail.
>
> The fix is to "vos remove" the backup volume. (Remember kids... don't
> forget to add the ".backup" or you'll be sorry.) This reports that the
> volume really doesn't exist on disk, but it goes ahead and deletes whatever
> is lying around that was causing "vos backup" to fail. (Probably just a VLDB
> entry. I haven't tried using "vos delentry" yet.)
>
> The frustrating discovery in this is that "vos backup" returns successfully
> and claims:
> Created backup volume for user.foo
> even though no backup volume was made. We never experienced this particular
> failure mode until AFS 3.1. Different verisons of AFS have had their
> peculiar failure modes so we at ECE do not use "vos backupsys". Rather we
> have each server collect a list of it's volumes and run "vos backup" on each
> one individually. By doing this, the program can analyze each individual
> failure and take the appropriate action.
>
> Dave Carrel
> ECE Facilities
>
It sounds like you are getting exactly the same failure I am. And yes, it is
most important that you don't forget the ".backup" :-). I'm waiting for it
to fail again so I can check the VolserLog...
Bob
