Quoting "Herbert Poetzl" <herbert@13thfloor.at>:
>> You are correct, it returns EINVAL:
>> readlink("/tmp/foo", 0x7fffc1482140, 4096) = -1 EINVAL (Invalid argument)
>
> hmm, this is unrelated, look for a 'mount' returning EINVAL :)
>
Ahem, yes that would help, here it is:
mount("/tmp/foo", "bar", 0x40d978, MS_MGC_VAL|MS_MOVE, NULL) = -1
EINVAL (Invalid argument)
>> Is there a way to fix it?
>
> well, you can talk to the mainline folks to 'allow'
> move mounts in shared namespaces or you could simply
> disable the check which blocks it (if that is the
> actual reason), or you could disable the shared
> mount space in util-vserver startup ...
I have simply no idea how to start taking this on. I'll do some
research and try to find the path of least resistance.
Cheers,
==
From Ben Green