Of course. Didn't look at the numeric IDs. I assume that's what happened here?
On 3/26/2012 2:19 PM, Derrick Brashear wrote: > On Mon, Mar 26, 2012 at 3:17 PM, Kim Kimball <[email protected]> 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. >> >> Dumping the .backup is not just a good practice, in my opinion, it is >> the only sensible practice if keeping writability is important. Large >> volumes can take a while to dump -- >> >> 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 ... >> >> It does look like more than one operation was in progress -- a volume >> delete isn't part of a volume dump > the temporary clone gets cleaned up at the end. > _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
