[657] in SIPB-AFS-requests

home help back first fref pref prev next nref lref last post

inconsistency in the sipb cell

daemon@ATHENA.MIT.EDU (Marc Horowitz)
Mon Apr 6 18:36:49 1992

To: sipb-afsreq@MIT.EDU
Cc: bug-afs@MIT.EDU
Reply-To: Marc Horowitz <marc@MIT.EDU>
Date: Mon, 06 Apr 92 18:35:44 EDT
From: Marc Horowitz <marc@MIT.EDU>

In doing the backup, we noticed that there were a few problems with
volumes in the sipb cell.  The symptoms looked like this:

<12> deathtongue:~> vos ex user.yandros -c sipb
user.yandros                      536872619 RW       6682 K  On-line
    ROSEBUD.MIT.EDU /vicepa
    Parent  536872619 Clone          0 Backup  536872621
    MaxQuota       7500 K
    Creation    Sun Jan  5 23:33:03 1992
    Last Update Mon Apr  6 17:29:50 1992
    8430 accesses in the past day

        readWriteID 536872619   valid
        readOnlyID  536872620   invalid
        backUpID    536872621   valid
    number of sites -> 1
    server ROSEBUD.MIT.EDU partition /vicepa RW Site

but:

<13> deathtongue:~> vos ex user.yandros.backup -c sipb
Could not fetch the information about volume 536872621 from the server
: No such device
Volume does not exist on the site indicated by the VLDB

user.yandros
        readWriteID 536872619   valid
        readOnlyID  536872620   invalid
        backUpID    536872621   valid
    number of sites -> 1
    server ROSEBUD.MIT.EDU partition /vicepa RW Site
Exit 1

Sure enough, the volume wasn't there.  I'm willing to believe things
can get out of sync, but there were two other bugs, which I believe
should be fixed:

<11> deathtongue:~> vos backup user.yandros -c sipb -verbose
Created backup volume for user.yandros

Note complete lack of any error.  But, compare with a working backup:

<10> deathtongue:~> vos backup user.marc -c sipb -verbose
Re-cloning backup volume 536872364 ...done
Created backup volume for user.marc

That's different, but I wouldn't notice them unless I happened to be
looking for a problem.  Running "vos syncvldb" did *not* notice that
the volume was missing from the disk, and did *not* remove it from the
vldb.  This is a bug.

To fix things, I had to explicitly remove the volume:

<15> deathtongue:~> vos remove rosebud a user.yandros.backup -c sipb -verbose

user.yandros
        readWriteID 536872619   valid
        readOnlyID  536872620   invalid
        backUpID    536872621   valid
    number of sites -> 1
    server ROSEBUD.MIT.EDU partition /vicepa RW Site
WARNING: Volume 536872621 did not exist on the disk
Marking the backup volume 536872621 deleted in the VLDB
Volume 536872621 on partition /vicepa server rosebud deleted

Note the WARNING.  Now, vos backup dtrt:

<16> deathtongue:~> vos backup user.yandros -c sipb -verbose
Creating a new backup clone 536872621 ...done
Created backup volume for user.yandros

		Marc

home help back first fref pref prev next nref lref last post