All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Zagrabelny <mzagrabe@d.umn.edu>
To: Matthew Warren <matthewwarren101010@gmail.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: subvolumes as partitions and mount options
Date: Mon, 27 Mar 2023 16:06:08 -0500	[thread overview]
Message-ID: <CAOLfK3Uokj64QcBypkfr7X79qQ9235o=bv87RJtRSKjupKUQLw@mail.gmail.com> (raw)
In-Reply-To: <CA+H1V9zb8aO_Y37vdwbubqHZds__=hLe06zx1Zz6zdsDLUkqeQ@mail.gmail.com>

Hi Matthew,

On Mon, Mar 27, 2023 at 3:32 PM Matthew Warren
<matthewwarren101010@gmail.com> wrote:
>
> If you want something like this, you will want to have those
> subvolumes outside of the root subvolume. For instance, My BTRFS
> subvolumes look like this
> / root subvol - The subvolume which is created on mkfs
> /@arch - The subvolume I have mounted as /
> /@home - The subvolume I have mounted as /home
>
> If you do something like that, then you prevent access by having it
> hidden in the root subvolume.

Do you know if I can retrofit my current btrfs install to implement
the structure you've suggested?

To my knowledge I've got my root filesystem mounted on the "parent" subvolume:

root@ziti:~# btrfs subvolume list / -a
ID 256 gen 606645 top level 5 path <FS_TREE>/@rootfs
ID 257 gen 606389 top level 256 path @rootfs/subv_content

root@ziti:~# mount | grep btrfs
/dev/nvme0n1p2 on / type btrfs
(rw,relatime,ssd,space_cache=v2,subvolid=256,subvol=/@rootfs)
/dev/nvme0n1p2 on /subv_mnt type btrfs
(rw,nosuid,nodev,noexec,relatime,ssd,space_cache=v2,subvolid=257,subvol=/@rootfs/subv_content)

The subv_content subvolume is just for testing and can be deleted.

Thanks for any pointers!

-m

  reply	other threads:[~2023-03-27 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 18:48 subvolumes as partitions and mount options Matt Zagrabelny
2023-03-27 19:25 ` Andrei Borzenkov
2023-03-27 19:50   ` Matt Zagrabelny
2023-03-27 20:24     ` Graham Cobb
2023-03-27 20:31     ` Matthew Warren
2023-03-27 21:06       ` Matt Zagrabelny [this message]
2023-03-28  1:42         ` Matthew Warren
2023-03-28 19:45           ` Matt Zagrabelny
2023-03-29  4:04             ` Andrei Borzenkov

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='CAOLfK3Uokj64QcBypkfr7X79qQ9235o=bv87RJtRSKjupKUQLw@mail.gmail.com' \
    --to=mzagrabe@d.umn.edu \
    --cc=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matthewwarren101010@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 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.