From: Robert White <rwhite@pobox.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Volume/subvolume UUID uniqueness, was: BTRFS messes up snapshot LV with origin
Date: Sat, 22 Nov 2014 14:55:08 -0800 [thread overview]
Message-ID: <5471144C.8090601@pobox.com> (raw)
In-Reply-To: <54711351.1040208@pobox.com>
On 11/22/2014 02:50 PM, Robert White wrote:
> Take a couple snapshots of a subvolume, and then
> send those subvolumes to another file system with send/receive, and then
> do "btrfs subvolume list -u -q" on the two filesystems and tell me that
> mess makes sense. Or try to recreate a subvolume from its snapshot in a
> way that doesn't shatter the relationships in your backup scheme. (I'm
> researching for a couple patches but I'm not expecting a warm reception
> given the silence to date).
(ASIDE In particular use "btrfs sub send -c SNAP1 SNAP2" and then "btrfs
sub send -c SNAP2 SNAP3" etc before doing the "btrfs sub list -u -q" to
view the mess I speak of.)
prev parent reply other threads:[~2014-11-22 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 19:52 Volume/subvolume UUID uniqueness, was: BTRFS messes up snapshot LV with origin Chris Murphy
2014-11-22 22:50 ` Robert White
2014-11-22 22:55 ` Robert White [this message]
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=5471144C.8090601@pobox.com \
--to=rwhite@pobox.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.