[162] in Info-AFS_Redistribution
No subject found in mail header
daemon@ATHENA.MIT.EDU (Mac Mathis)
Wed Jun 19 08:51:45 1991
Date: Wed, 19 Jun 91 07:03:25 CDT
From: mamathis@inetnode.austin.ibm.com (Mac Mathis)
To: Info-AFS@transarc.com, Re:@inetnode.austin.ibm.com,
To: Info-AFS@transarc.com
Subject: Missing Backup Volumes
>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
>
You should be very careful even removing the .backup. I recommend you
clone both the parent and the backup (use vos dump piped to vos restore)
before you start removing volumes. I had been doing this same thing and
yesterday it bit me. After I did the remove of the .backup volume, the
parent volume was garbage. Even a salvage failed to restore the volume
to anything readable.
Mac Mathis
