"Jean-Ray Arseneau": > Here=E2=80=99s the updated log after applying the latest debug b.patch:
Thank you very much. I think I could see the scenario. As you might know, the mfs policy caches the free-space value per branch, and pmfsrr policy internally runs the mfs rourtine twice. The first one is considering the parent dir, and the other is without considering the parent. In this second call, the mfs routine doesn't work expectedly since the result is cached and the routine dicide the target bracnh based upon the last result. Obviously it is an aufs bug. I will adress it in next week. If you can't wait, try 'pmfdrr:<low>:0' which will force the mfs routine not to use the cached value. J. R. Okajima ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
