>
> The other day, I moved all of the volumes on one partition over to another
> partition. The only file I did not move, but actually removed, was
> disk.afs1.a. I newfs'd the clean partition and re-mounted it. Now when
> I go to do backups, I get:
>
> Could not start a transaction on the volume 536870960
> Volume not attached, does not exist, or not on line
> Could not backup disk.afs1.a
>
> I have tried using ``vos zap'' to nuke all references to disk.afs1.a,
> but it still seems to be lingering.
>
> My questions:
>
> 1. What ARE these volumes that AFS creates (disk.afs1.a)? What
> are they used for?
>
> 2. Now that I have wiped the partition clean, what should I do
> about the fact that the backup process is still trying to find
> the file(s) ? I have issued a ``vos syncvldb'', and that did
> not seem to help. The file server processes have also been
> restarted since then.
Try a "vos delentry disk.afs1.a". I'll bet its still in the vldb. When you
dump a volumeset, it queries the vldb to get a list of volumes that satisfy the
volumeset. AFS does not create these volumes. Someone there must have done
that when they put the disk into service.
Mark Giuffrida
Univ of Michigan
[EMAIL PROTECTED]
