From: Goffredo Baroncelli <kreijack@inwind.it>
To: Remi Gauvin <remi@georgianit.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: WG: How to properly setup for snapshots
Date: Mon, 21 Dec 2020 21:52:39 +0100 [thread overview]
Message-ID: <4058703a-8cbc-3ceb-c9e7-08fcaaa2d8aa@inwind.it> (raw)
In-Reply-To: <e4622aa3-2c38-f389-1e2a-aa29009f9b5e@georgianit.com>
On 12/21/20 9:27 PM, Remi Gauvin wrote:
> On 2020-12-21 3:14 p.m., Goffredo Baroncelli wrote:
>
>> A subvolume can be moved everywhere with a simple 'mv' command.
>>
>
> No, they can not,, try this again with a *read only* snapshot
>
The topic was about why put the subvolumes/snapshots in another subvolume.
A readonly snapshot can't be moved from its parent (doesn't matter if it is a diretory or a subvolume). This is true. But the subvolume containing a readonly snapshot can be moved :
$ btrfs sub crea sub1
Create subvolume './sub1'
$ btrfs sub crea sub2
Create subvolume './sub2'
$ mkdir dir1
$ btrfs sub snap -r sub2 sub1/snap2
Create a readonly snapshot of 'sub2' in 'sub1/snap2'
$ btrfs sub snap -r sub2 dir1/snap2
Create a readonly snapshot of 'sub2' in 'dir1/snap2'
$ mv sub1 sub1-renamed
$ mv dir1 dir1-renamed
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2020-12-21 20:59 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
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 [this message]
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=4058703a-8cbc-3ceb-c9e7-08fcaaa2d8aa@inwind.it \
--to=kreijack@inwind.it \
--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