From: Mark Corbin <mcorbin@lunarenergy.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-unionfs@vger.kernel.org
Subject: Re: overlayfs - vaild to mount mergedir over lowerdir?
Date: Fri, 31 Oct 2025 14:29:34 +0000 [thread overview]
Message-ID: <CAPfD7wkucaZRtuaHhPmNHJjc4_SNuCtc+TatChBrpJS2Sb-WVw@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxhbdE-HE5wX2nJ3oFy++BJqSWctwaoXGnk=-1hTp8VOvg@mail.gmail.com>
On Thu, 30 Oct 2025 at 17:54, Amir Goldstein <amir73il@gmail.com> wrote:
>
> On Thu, Oct 30, 2025 at 6:26 PM Mark Corbin <mcorbin@lunarenergy.com> wrote:
> >
> > Hello
> >
> > Is it valid/safe to mount an overlayfs mergedir over the lowerdir?
> >
> > The Yocto/OE mount-copybind script does exactly that:
> >
> > overlay on /srv type overlay
> > (rw,relatime,lowerdir=/srv,upperdir=/var/volatile/srv,workdir=/var/vola
> > tile/.srv-work)
> >
> > I wanted to do something similar with a read-only /etc where the
> > merged /etc is mounted on /etc, e.g.
> > mount -v -t overlay overlay -o
> > lowerdir=/etc,upperdir=/data/etc,workdir=/data/etc-work /etc
> >
> > Any issues or recommendations?
>
> None that I can think of.
> Overlayfs has no problem with that.
> It gets a reference to the lowerdir object at mount time *before*
> attaching itself to the mount point and that's it.
>
> Thanks,
> Amir.
Thanks Amir.
--
Mark Corbin
Senior Software Engineer | lunarenergy.com | LinkedIn | Instagram
--
C2:Restricted unless otherwise stated.
--
Lunar Energy Limited is a company registered in England and Wales,
authorised and regulated by the Financial Conduct Authority under reference
number 767876. Company registration number: 05631091. Registered office: 55
Baker Street, London, England, W1U 7EU
prev parent reply other threads:[~2025-10-31 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:25 overlayfs - vaild to mount mergedir over lowerdir? Mark Corbin
2025-10-30 17:54 ` Amir Goldstein
2025-10-31 14:29 ` Mark Corbin [this message]
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=CAPfD7wkucaZRtuaHhPmNHJjc4_SNuCtc+TatChBrpJS2Sb-WVw@mail.gmail.com \
--to=mcorbin@lunarenergy.com \
--cc=amir73il@gmail.com \
--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).