All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume clone or fork (btrfs-progs feature request)
Date: Thu, 9 Jul 2015 14:58:00 +0000 (UTC)	[thread overview]
Message-ID: <pan$80db3$57bc5aa6$1bb3a1f9$e86b9507@cox.net> (raw)
In-Reply-To: 20150709135448.GH10539@carfax.org.uk

Hugo Mills posted on Thu, 09 Jul 2015 13:54:48 +0000 as excerpted:

> On Thu, Jul 09, 2015 at 01:43:53PM +0000, Duncan wrote:
>> I could have sworn btrfs property -t subvolume can get/set that
>> snapshot bit.  I know I saw the discussion and I think patch for it go
>> by, but again, as I don't use them, I haven't tracked closely enough to
>> see if it ever got in.
> 
> Are you thinking of the read-only flag? That's not the same thing
> as the various UUID properties (e.g. parent) which can be used to
> detemine if a subvolume was made using a snapshot.

Perhaps, but I was sure there was a snapshot property too, because I 
remember discussion of being able to unset it in ordered to remove it 
from the snapshot (only) list.

But maybe that's all it was, discussion, it wasn't implemented, and I 
ended up conflating it with the read-only bit, which /can/ be set/unset 
that way.  Like I said I can't check as I don't have any subvolumes/
snapshots available to do a listing on and see, and the property manpage 
doesn't have a properties list to check on, it wants you to use the list 
option to get the list.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-07-09 14:58 UTC|newest]

Thread overview: 17+ 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
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 [this message]
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
2015-06-25 20:47 james harvey
2015-06-25 20:59 ` 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='pan$80db3$57bc5aa6$1bb3a1f9$e86b9507@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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.