On Wed, 21 Nov 2012 16:56:58 +0000 Neil Davies <[email protected]> wrote:
> backup volrestore -server afsfs4 -part a -vol xxxxxxx -date "11/15/2012 > 00:02" -ext .b -portoffset 1 -localauth [...] > Wed Nov 21 11:15:47 2012 Volume 536872199 offline: not in service I'm not looking at the code at the moment, but my educated guess would be that the backup process tries to restore the initial volume dump and in the incrementals without "online"-ing the volume, so you can't access it between the restores. When we're done with the first restore, we give the volume back to the fileserver, but since inService isn't set, it fails to attach. So when the volserver asks for the vol again for the incremental restores, the fileserver says it doesn't exist, the volserver sees it does exist on disk, so it bails. The immediate error seems to be coming from 939382c5c1622750665a9f543168bd3b8044583f; the non-DAFS fileserver historically has been able to attach non-inservice/non-blessed volumes, I think, but it just doesn't serve them to clients. Reverting that may or may not be enough to solve this. If you want a workaround/fix without changing code, you can try switching the fileserver to DAFS. If this already is DAFS, then please say so because some of the stuff I just said is wrong :) -- Andrew Deason [email protected] _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
