From: Nicholas Hubbard <nicholashubbard@posteo.net>
To: linux-unionfs@vger.kernel.org
Subject: Support for including nested mountpoints in overlay?
Date: Fri, 12 Sep 2025 15:32:29 +0000 [thread overview]
Message-ID: <87plbvadpw.fsf@slackpad.slackpad.domain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hello everybody,
I have just started working with overlayfs, and ran into a problem. Specifically
I wanted to overlay the root of my filesystem with a command like the following:
# mount -t overlay overlay -o lowerdir=/,upperdir=./tmp-upper,workdir=./tmp-work ./merged
However, I noticed that my nested btrfs subvolumes and boot partition were not
included in ./merged. I quickly learned though that you could have multiple
lowerdirs. So next I tried the following command (I have a nested btrfs subvolume
at /home, and my boot partition mounted at /boot):
# mount -t overlay overlay -o lowerdir=/:/home:/boot,upperdir=./tmp-upper,workdir=./tmp-work ./merged
I was expecting that now I would have (for example) the following directories:
./merged/home/$USER
./merged/boot/grub
However I instead had:
./merged/$USER
./merged/grub
Which shows that all the lowerdirs are placed right at the root of the mergedir.
So I have two questions.
1. Is there a (easy) way say "I want to include all nested mountpoints into the
overlay in their same directories"?
2. If there is not a (easy) way to do this, do you think it would be both feasible
and useful to add such a feature?
If the answer to question 2 is "yes", then I would be happy to take a try at this :)
--
Nicholas B. Hubbard
Keys: https://github.com/NicholasBHubbard/public-keys
Key ID: 508022AE06C2C446D8072447C700A066BB25F148
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2025-09-12 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 15:32 Nicholas Hubbard [this message]
2025-09-13 4:21 ` Support for including nested mountpoints in overlay? Amir Goldstein
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=87plbvadpw.fsf@slackpad.slackpad.domain \
--to=nicholashubbard@posteo.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.