[Bug 9946] mv is corrupting files on aufs filesystem (e.g. used by open-source docker V17.03)

bugzilla at busybox.net bugzilla at busybox.net
Sun Jun 11 10:01:18 UTC 2017


--- Comment #2 from Bernhard Reutner-Fischer <aldot at uclibc.org> ---
>From http://aufs.sourceforge.net/aufs.html

To rename(2) directory may return EXDEV even if both of src and tgt are on the
same aufs. When the rename-src dir exists on multiple branches and the lower
dir has child(ren), aufs has to copyup all his children. It can be recursive
copyup. Current aufs does not support such huge copyup operation at one time in
kernel space, instead produces a warning and returns EXDEV. Generally, mv(1)
detects this error and tries mkdir(2) and rename(2) or copy/unlink recursively.
So the result is harmless. If your application which issues rename(2) for a
directory does not support EXDEV, it will not work on aufs. Also this
specification is applied to the case when the src directroy exists on the lower
readonly branch and it has child(ren).

You are receiving this mail because:
You are on the CC list for the bug.

More information about the busybox-cvs mailing list