Lou Gosselin: > You mention lsof, but I don't think it can identify which file handles > are responsible for blocking a specific aufs branch (my former post had > an example of this).
Do you mean that you want to find the "tail" process accessing "branch1_file", ie. want to make sure that "union/branch1_file" exists in branch1 but "branch2_file"? For such case, people runs "ls branch1 branch2" usually. In old aufs1 era, there was a script called "unionctl" which has a query operation. If you run "unionctl --query1 branch1_file", it shows "branch1". > To do a "-o del:X", doesn't one have to kill all file locks on the > union, even those which aren't blocking X? > > If the answer above is "no", then I'm afraid I still don't understand > how to identify just those file locks which are blocking changes to X. > (Of course, this is somewhat untrue now that I'm aware of the debugging > sysreq). Of course, the answer is no. Usually "lsof" is enough for such case I think, because users can find which file exists in which branch easily. "ls /the/file/path/under/all/branches" will help too. Isn't it enough for you? J. R. Okajima ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/
