From: Roman Mamedov <rm@romanrm.net>
To: Remi Gauvin <remi@georgianit.com>
Cc: Claudius Ellsel <claudius.ellsel@live.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: WG: How to properly setup for snapshots
Date: Mon, 21 Dec 2020 22:37:01 +0500 [thread overview]
Message-ID: <20201221223701.0845e9ad@natsu> (raw)
In-Reply-To: <a68cd516-d6a2-b7ee-744b-d1b0ee83c2df@georgianit.com>
On Mon, 21 Dec 2020 12:05:37 -0500
Remi Gauvin <remi@georgianit.com> wrote:
> I suggest making a new Read/Write subvolume to put your snapshots into
>
> btrfs subvolume create .my_snapshots
> btrfs subvolume snapshot -r /mnt_point /mnt_point/.my_snapshots/snapshot1
It sounds like this could plant a misconception right from the get go.
You don't really put snapshot* "into" a subvolume. Subvolumes do not actually
contain other subvolumes, since making a snapshot of the "parent" won't
include any content of the subvolumes with pathnames below it.
As such there's no benefit in storing snapshots "inside" a subvolume. There's
not much of the "inside". Might as well just create a regular directory for
that -- and with less potential for confusion.
* - keep in mind that "snapshot" and "subvolume" mean the same thing in Btrfs,
the only difference being that "snapshot"-subvolume started its life as
being a full copy(-on-write) of some other subvolume.
--
With respect,
Roman
next prev parent reply other threads:[~2020-12-21 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9P191MB165033908B55F8312178D90AE2CB0@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM>
2020-12-21 16:11 ` WG: How to properly setup for snapshots Claudius Ellsel
2020-12-21 17:05 ` Remi Gauvin
2020-12-21 17:37 ` Roman Mamedov [this message]
2020-12-21 18:14 ` Remi Gauvin
2020-12-21 20:14 ` Goffredo Baroncelli
2020-12-21 20:27 ` Remi Gauvin
2020-12-21 20:52 ` Goffredo Baroncelli
2020-12-21 18:26 ` Andrei Borzenkov
2020-12-21 18:35 ` AW: " Claudius Ellsel
2020-12-21 18:40 ` Andrei Borzenkov
2020-12-21 20:51 ` AW: " Claudius Ellsel
2021-01-06 20:07 ` Ulli Horlacher
2020-12-21 20:24 ` WG: " Goffredo Baroncelli
2020-12-21 18:04 ` AW: " Claudius Ellsel
2020-12-21 18:32 ` Remi Gauvin
2020-12-21 18:39 ` AW: " Claudius Ellsel
2020-12-21 20:45 ` Claudius Ellsel
2020-12-21 23:33 ` Graham Cobb
2020-12-22 15:19 ` AW: " Claudius Ellsel
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=20201221223701.0845e9ad@natsu \
--to=rm@romanrm.net \
--cc=claudius.ellsel@live.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.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