From: Roman Mamedov <rm@romanrm.net>
To: Rich Rauenzahn <rrauenza@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Combining two filesystems into single pool
Date: Wed, 27 Jul 2022 02:40:15 +0500 [thread overview]
Message-ID: <20220727024015.3e87bb13@nvm> (raw)
In-Reply-To: <CAG+QAKUu6TXJqoq=eQczE+CWJCL06bN8oymbSFQVCzXto+fzyQ@mail.gmail.com>
On Tue, 26 Jul 2022 13:32:22 -0700
Rich Rauenzahn <rrauenza@gmail.com> wrote:
> Could I, say, move /A to a subvolume A in itself and then permanently
> "connect" /B as a subvolume B, putting all the disks into a single
> pool? And then mount the two subvolumes as /A and /B?
>
> I'd swear I'd seen instructions on how to combine filesystem pools
> before, but I can't find it again.
Check out MergerFS.
Although that adds a FUSE layer on top of both filesystems, which might be
fine for a home media library, but maybe not for some other uses.
--
With respect,
Roman
next prev parent reply other threads:[~2022-07-26 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 20:32 Combining two filesystems into single pool Rich Rauenzahn
2022-07-26 21:02 ` David Sterba
2022-07-26 21:40 ` Roman Mamedov [this message]
2022-07-28 7:19 ` Robert Krig
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=20220727024015.3e87bb13@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=rrauenza@gmail.com \
/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