On Mi, 23.07.2014, 14:02, Miklos Szeredi wrote: > On Wed, Jul 23, 2014 at 1:57 PM, Klaus Kreil <klaus.kreil@xxxxxxxxxxxx> > wrote: > >>> You need to give absolute paths: >>> >>> mount -t overlayfs overlayfs -o >>> lowerdir=/mnt/root_ro,upperdir=/mnt/root_rw/upper,workdir=/mnt/root_rw/work >>> /mnt/root >>> >> Thanks Miklos, >> I had tried that before, but that did not/does not work as well. The new >> command (adjusted to my environment and from within the rescue-shell and >> all within a single line) was: >> # mount -t overlayfs overlayfs -o >> lowerdir=/mnt/root_ro,upperdir=/mnt/root_rw,workdir=/mnt/root_rw/.work >> /mnt/root >> >> The new error message from dmesg now reads: >> [ 1369.069178] overlayfs: workdir and upperdir must be separate subtrees > > Exactly. Observe that I used upperdir=/mnt/root_rw/upper. I see what you mean and I have to admit, that slipped my eye. This however triggers an additional question: Would this now require me to create an new "virtual" root directory (in your case named "upper") on my upperdir filesystem and move everything that was in the real root of the existing upperdir filesystem to the new virtual root directory? In other words now - and contrary to the old behaviour - overlaying one root directory of a filesystem onto another root directory of another filesystem is no longer possible. If that's the case, I guess lost+found should nevertheless stay in the real root directory of the upperdir? Furthermore that would als mean that the workdir is never visible from within the combined tree and therefore I could go away with the .work and rename the workdir to work. Thanks again for your help, Klaus -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
