Re: FSFS locks questions and a concern

Daniel Shahaf <d.s_at_daniel.shahaf.name> writes:

> 3. What's a reasonable strategy to hotcopy the locks?
>
> I've started on a patch that uses walk_digest_files() (I modified
> that function today), but currently that patch simply does a walk
> starting at the digest file md5("/"), and consequently it misses
> copying the unreferenced digest file md5("/trunk").

It appears you have to read/copy md5("/") and get a list of locks, then
read/copy each lock file that still exists, then reconstruct the
intermediate files for the locks that were copied.

-- 
Philip