From: David Sterba <dsterba@suse.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: sander@humilis.net, "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: Wed, 15 Jul 2015 14:01:57 +0200 [thread overview]
Message-ID: <20150715120157.GF6306@suse.cz> (raw)
In-Reply-To: <559FCA6D.8020800@gmail.com>
On Fri, Jul 10, 2015 at 09:36:45AM -0400, Austin S Hemmelgarn wrote:
> > Technically it's not really a bit. The snapshot relation is determined
> > by the parent uuid value of a subvolume.
> I'm actually kind of curious, is the parent UUID actually used for
> anything outside of send/receive?
AFAIK no.
> >> which in turn means that certain
> >> tasks are more difficult to script robustly.
> >
> > I don't deny the interface/output is imperfect for scripting purposes,
> > maybe we can provide filters that would satisfy your usecase.
> >
> Personally, I don't really do much direct scripting of BTRFS related
> tasks (although that might change if I can convince my boss that we
> should move to BTRFS for our server systems). Most of my complaint with
> the current arrangement is primarily aesthetic more than anything else.
Ok understood, thanks.
next prev parent reply other threads:[~2015-07-15 12:01 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
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 [this message]
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=20150715120157.GF6306@suse.cz \
--to=dsterba@suse.com \
--cc=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 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.