Adam.Fox@netapp.com writes
Let me be the first to say, I could be wrong here, but since 6.0 allows you to offline a volume without rebooting the filer should be able to revert it back without affecting any other volumes. I believe that's what the error message is telling you...
That was my immediate reaction on seeing the original posting as well!
But why isn't reversion of an *offline* volume, which is about to be completely overwritten by "vol copy", essentially an instantaneous thing? Maybe if I understood these zone checksums better it would be clearer, but I can see why it takes time to make them correct, but not why it should take any time to discard them.
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.