[229] in SIPB-AFS-requests
root.afs
daemon@ATHENA.MIT.EDU (qjb@ATHENA.MIT.EDU)
Sun Jun 3 11:46:51 1990
From: qjb@ATHENA.MIT.EDU
Date: Sun, 3 Jun 90 11:46:32 -0400
To: sipb-afsreq@ATHENA.MIT.EDU
I did this on Friday, but I had to log out quickly and haven't
logged in since then until now.
Even after I restored root.afs and released the volume, the same
problems seemed to exist with it. I've seen this kind of thing
happen a few times before. I was going to rename the old one so
that it could be inspected, but I forgot to do that.
What I ended up doing was the following:
vos remove the volume
Look on the c and e partitions with vos listvol. Notice
root.afs.backup, root.afs.readonly. I then vos zapped those.
Once all trace of the volumes were gone, I recreated with a vos
restore from a dump of athena.mit.edu:root.afs, recreated the
two replication sites, released, and re-backed up. I suppose
that since the read-write volume of root.afs in sipb was okay it
probably would have worked to dump that and restore it.
This happenned to several volumes in soup's cell a while after I
updated it from pre-alpha to 3.0A to 3.0B.
Jay
