On Wed, Apr 01 2015, sf...@users.sourceforge.net wrote: > How was the configuration? > If CONFIG_AUFS_XATTR is enabled, try this patch and specify 'verbose' > option when mounting aufs. It will print the xattr name. If XATTR (ACL) > causes the problem, then this patch and 'verbose' will tell us. > > # mount -t aufs -o br:$tmp/rw=rw:$tmp/nfs=ro,verbose aufs $tmp/union
CONFIG_AUFS_XATTR is enabled. Adding verbose (and/or -v) doesn't print
anything that I could find, do I need another option for verbose? or
where should it be printed?
>
> If CONFIG_AUFS_XATTR is disabled, then XATTR/ACL is not the problem. I'd
> ask you to enable CONFIG_AUFS_DEBUG and run
>
> # echo 1 > /sys/module/aufs/parameter/debug
> mv -v $tmp/union/a/{b,c}
> # echo 0 > /sys/module/aufs/parameter/debug
I've enabled debug (for the mount as well). For good measure, I'm
attaching all the relevant data (including dmesg output). The kernel is
3.19.3 with the patch you sent, and the only aufs mounted is the one
after running the script (when not unmounting it).
In the coming week, I probably won't have much time to check this
further.
Yair.
aufs.data.tgz
Description: application/gtar-compressed
------------------------------------------------------------------------------ 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/
