From: Miklos Szeredi <miklos@szeredi.hu>
To: Klaus Kreil <klaus.kreil@univie.ac.at>
Cc: linux-unionfs@vger.kernel.org
Subject: Re: overlayfs v22 on kernel 3.15.5
Date: Wed, 23 Jul 2014 14:02:49 +0200 [thread overview]
Message-ID: <CAJfpegsc4swQ2e7LfKbzHYCoa3thvetLhydzqr1My2PJr=Myag@mail.gmail.com> (raw)
In-Reply-To: <207df75d465c4b3fe95b6a90f3531905.squirrel@webmail.univie.ac.at>
On Wed, Jul 23, 2014 at 1:57 PM, Klaus Kreil <klaus.kreil@univie.ac.at> 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.
Thanks,
Miklos
next prev parent reply other threads:[~2014-07-23 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJfpeguH=BmevY+SM8HKBATS7B+htcX7_WLRiMFmypW_D-424Q@mail.gmail.com>
[not found] ` <3a4b4cc25d1a8325934ba439d4777c35.squirrel@webmail.univie.ac.at>
2014-07-23 11:48 ` overlayfs v22 on kernel 3.15.5 Miklos Szeredi
2014-07-23 11:50 ` Miklos Szeredi
2014-07-23 11:57 ` Klaus Kreil
2014-07-23 12:02 ` Miklos Szeredi [this message]
2014-07-23 12:15 ` Klaus Kreil
2014-07-23 13:33 ` Miklos Szeredi
2014-07-23 15:44 ` Klaus Kreil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJfpegsc4swQ2e7LfKbzHYCoa3thvetLhydzqr1My2PJr=Myag@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=klaus.kreil@univie.ac.at \
--cc=linux-unionfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).