linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: sander@humilis.net
Cc: "Fajar A. Nugraha" <list@fajar.net>,
	james harvey <jamespharvey20@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs subvolume clone or fork (btrfs-progs feature request)
Date: Thu, 09 Jul 2015 08:48:00 -0400	[thread overview]
Message-ID: <559E6D80.7010607@gmail.com> (raw)
In-Reply-To: <20150709124121.GA25033@panda>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On 2015-07-09 08:41, Sander wrote:
> Austin S Hemmelgarn wrote (ao):
>>> What's wrong with "btrfs subvolume snapshot"?
>>
>> Well, personally I would say the fact that once something is tagged as
>> a snapshot, you can't change it to a regular subvolume without doing a
>> non-incremental send/receive.
>
> A snapshot is a subvolume. There is no such thing as "tagged as a
> snapshot".
>
> 	Sander
>
No, there is a bit in the subvolume metadata that says whether it's 
considered a snapshot or not.  Internally, they are handled identically, 
but it does come into play when you consider things like btrfs subvolume 
show -s (which only lists snapshots), which in turn means that certain 
tasks are more difficult to script robustly.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]

  reply	other threads:[~2015-07-09 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  1:20 btrfs subvolume clone or fork (btrfs-progs feature request) james harvey
2015-07-09  6:22 ` Fajar A. Nugraha
2015-07-09 12:07   ` Austin S Hemmelgarn
2015-07-09 12:41     ` Sander
2015-07-09 12:48       ` Austin S Hemmelgarn [this message]
2015-07-09 12:58         ` Sander
2015-07-09 13:43         ` Duncan
2015-07-09 13:54           ` Hugo Mills
2015-07-09 14:58             ` Duncan
2015-07-09 15:04         ` Roman Mamedov
2015-07-09 18:33         ` David Sterba
2015-07-10 13:36           ` Austin S Hemmelgarn
2015-07-15 12:01             ` David Sterba
2015-07-10 13:01 ` David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2015-07-09  1:19 james harvey

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=559E6D80.7010607@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=jamespharvey20@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    --cc=sander@humilis.net \
    /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;
as well as URLs for NNTP newsgroup(s).