Excerpts from internet.info-afs: 12-Jan-98 Severely Broken Volumes by
Jeff [EMAIL PROTECTED]
> VLDB: entry is deleted (soft delete)
While I can't figure out how this happened, I do know of something that
should fix it. In order to do so, you need a copy of the 'vlclient'
utility which is not normally included in AFS binary releases. If you
have a source license, it's in the 'vlserver' directory, and can be
compiled as follows:
touch /tmp/AFS_component_version_number.c
cc -o vlclient vlclient.c -I. -I/tmp -I$(AFSWS)/include/afs
-L$(AFSWS)/lib/afs -lvldb -lubik -lauth -lsys -lrxkad -lrx -llwp -ldes
-lcmd -lcom_err $(AFSWS)lib/afs/util.a <libraries for your OS>
rm /tmp/AFS_component_version_number.c
If you don't have a source license, you might be able to get transarc to
give you a binary...
To fix a soft deleted volume, you should be able to use vlclient as
follows (where 0 represents 'Read Write volume', 1 would be ReadOnly, 2
Backup)
% vlclient -cell andrew.cmu.edu
vl> undelete 1970723513 0
Searching vldb for volume 1970723513...
The current contents of the vldb for 1970723513:
Entry for volume name: user.cg2v, volid=1970723513 (flags=5000) are:
ParentID=1970723513, ReadOnlyID=0, backupID=1970723515, CloneId=0 nServers=1
ServerNumber ServerPart serverFlag
2147617284 2 4
Entry not deleted; ignored
^^^^^^^^^^^^^^^^^^^^^^^^^^
As I can't generate one of these volumes easily, I haven't tested to
make sure this works, but it looks like it should.
