Brenden Carvalho:
> The policy should be similar to create=mfs,
> But instead of writing to the branch in order of free space,
> It should write to the highest branch. If that highest branch gets full, it
> can write to the next highest branch
Hmm, I remember that I have discussed such feature in 2010.
As you might know, the default policy is
.B create=tdp | top\-down\-parent
Select the highest branch where the parent dir exists. If this
branch is not writable, internal copyup will happen.
The policy for this copyup is always `bottom\-up.'
This is the default policy.
If I add a new policy "top-down" which is similar to "top-down-parent"
but doesn't care about the parent dir. Also another new policy
"top-down-free-space[:low]" may be good. The optional parameter is
similar to "create=mfsrr:low[:second]", but this new policy will try
next in the branch hierarchy.
.B create=mfsrr:low[:second]
Selects a writable branch in most\-free\-space mode first, and then
round\-robin mode. If the selected branch has less free space than the
specified value `low' in bytes, then aufs re-tries in round\-robin mode.
.\" `G', `M' and `K' (case insensitive) can be followed after `low.' Or
Try an arithmetic expansion of shell which is defined by POSIX.
For example, $((10 * 1024 * 1024)) for 10M.
You can also specify the duration (`second') which is equivalent to
the `mfs' mode.
> Is it possible to implement such a feature?
Possible.
But unfortunately I don't have enough time to do it. Can you wait for a
few months?
J. R. Okajima
------------------------------------------------------------------------------
