On 8/5/2019 4:37 PM, [email protected] wrote: > Hello every1, > > a (maybe) minor problem I'm getting with OpenAFS and I'm quite lost, what to > do. Given are 2 nodes running OpenAFS 1.8.2 on a Linux system.
> [...] > Doing a "vos release" for "root.vids", I get: > > --- SNIP --- > Failed to clone the volume 536870938 > Volume not attached, does not exist, or not on line > Error in vos release command. > Volume not attached, does not exist, or not on line > --- SNIP --- The OpenAFS volserver does not convey useful error details to the vos tool. Nor does the OpenaFS vos indicate to you which server the error was returned from. You need to examine the VolserLog file on both servers to identify the actual error. > While it works for all other volumes without any problem. I've already > removed "server2" and added it again, though without any change. You are assuming that the problem occurred on server2 when it might have occurred on server1. Since there is no RO site on server1 the vos tool will attempt to create a clone for the purpose of replicating it. [...] > I can successfully access the data through the client, though the release > process fails for this volume. You are most likely accessing the RW volume not the RO volume. Examine the VolserLog files and report back what you find. If there are no useful details, raise the log level to 125 on both volservers and re-attempt the release. Then examine the VolserLog files. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
