"Leslie P. Polzer":
> > For instance, with two RW branches,
> > - write(2) may return ENOSPC(No space left on device), while df reports
> > there left free space.
> > - on the contrary, df reports the filesystem is full or more than 100%,
> > write(2) may success.
>
> How might those happen? I'm only a casual (and new) user to aufs,
> so please bear with me. :)
Let's assume your aufs has two writable branches,
/aufs = /rw1 (free 0%) + /rw2 (free 50%)
- If aufs returns the sum for statfs(2), df(1) will show you enough free
space. But the writing file exists on the first branch and write(2)
will return an error of ENOSPC.
- If aufs does not return the sum for statfs(2), df(1) will show you no
more free space. But the writing file may exist on the second branch
and write(2) will success in this case.
According to what you wrote, your aufs seems having one tmpfs and one
squashfs or something. In this case the lower readonly branch is always
full, and df(1) with 'sum' option will work for you.
> > Do you think these options are useful?
>
> Yes, definitely!
Ok, I will try implement it in next Monday release.
Junjiro R. Okajima
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
