[OpenAFS] Re: 'vos dump' destroys volumes?

[Kim Kimball]

You're right, but the cloning is fast ... so avoids most of the
writability issue, esp for large volumes ...

As for 'vos' ... lol -- maybe I should try _reading_ what's been
written.  Sheesh.

Thx.

Kim


On 3/26/2012 2:02 PM, Andrew Deason wrote:
> On Mon, 26 Mar 2012 13:17:14 -0600
> Kim Kimball <dhk@ccre.com> wrote:
>
>> Dumping the RW volume makes it "busy" during the dump, which makes the
>> volume unwritable -- and generates "afs: Waiting for busy volume" errors
>> when a write occurs.
> Matthias used the -clone option, which should avoid that. The volume
> will not be writeable during the clone operation, though.
>
>> Identifying the software version that is running is better done with
>> "rxdebug" -- it's a nit, but the binaries are not guaranteed to be the
>> same as what's running -- and the "strings | grep" approach only tells
>> you what version the binary is, and not what the running version is ...
> Yeah yeah; that can be a tad inconvenient for 'vos', though :)
>