On 07/26/2010 01:38 AM, sf...@users.sourceforge.net wrote: > Lou Gosselin: > >> I tried the verbose option, but it doesn't produce enough output. >> > Generally speaking, it is enough. > If you know that a file is still opened when you delete the branch, then > you can find which process opens which file by lsof(1). >
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). > If remount,mod:a=ro returns EBUSY, it means a file is opened for writing. > If you think about the behaviour of unmouting ext2, you would agree this > behavour is enough. > > 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). I'm not requesting a change here, but if there is an existing way to do this, I would like to know how. Thanks, Lou ------------------------------------------------------------------------------ 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/
