Miklos,
We met a LXC issue [1] with overlayfs in Ubuntu, but with aufs it is gone.
I suspect it's related to the issue you mentioned in Documentation of overlayfs:
--
Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory
object in overlayfs will not contain vaid absolute paths, only
relative paths leading up to the filesystem's root. This will be
fixed in the future.
--
Could you please help to take a look at this? or point me out some hints.
[1], https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352
Thanks,
--
Bryan Wu <[email protected]>
Kernel Developer +86.186-168-78255 Mobile
Canonical Ltd. http://www.canonical.com
Ubuntu - Linux for human beings | http://www.ubuntu.com
Bryan Wu <[email protected]> writes:
> Miklos,
>
> We met a LXC issue [1] with overlayfs in Ubuntu, but with aufs it is gone.
>
> I suspect it's related to the issue you mentioned in Documentation of overlayfs:
> --
> Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory
> object in overlayfs will not contain vaid absolute paths, only
> relative paths leading up to the filesystem's root. This will be
> fixed in the future.
> --
>
> Could you please help to take a look at this? or point me out some hints.
>
> [1], https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352
To explain this a little background is needed about how overlayfs works.
Unlike a "true" union filesystem like AUFS, the overlayfs filesystem
doesn't actually contain any non-directory files. So when you open a
regular file, for example, what you get is actually the real file on the
upper or lower filesystems, not a file in the overlayfs. This is the
most important difference between overlayfs and aufs.
Currently overlayfs creates private clones of the lower and upper mounts
and uses those internally when opening a file. This results in
/proc/PID/fd showing not the expected path.
Instead of using private mount clones, overlayfs could add these mounts
to the same mountpoint as the overlayfs itself (under the overlayfs)
which would result in the correct path being printed. But to make this
consistent new logic would need to be added to namespace.c so that these
auxillary mounts are properly cleaned up on umount, and they are
properly copied/moved during mount binding/moving or namespace cloning.
Thanks,
Miklos