Hello David, David De Weerdt: > Suppose I have an aufs with two rw-mounted branches. Is it possible to > force writing to only the second branch, even if does not have the most > free space?
You can make a trick for the default policy 'top-down-parent'. - you have two writable branches - mkdir a directory on the lower branch for example, if you want to put dirA/fileB on the lower branch, then run "mkdir /lower/dirA". in this situation, when you try creating dirA/fileB, aufs finds that dirA already exists on the lower writable branch and the 'top-down-parent' policy will choose it as the target branch. But this approach may be unusable for you since you have to mkdir several times. So you may want another one. For instance, the copy-down or move-down feature may sound good for you (while they are just plan). But I don't understand what you need. What and how do you think the rule to choose your writable branch, which aufs can implement? By the way, I have a plan to implement a new option to specify the priority of the writable branches for a long time, and it is still just a plan. J. R. Okajima ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j
