linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Vance <za3k@za3k.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-send -c fails: reproduction case
Date: Sat, 16 Apr 2016 13:08:17 -0700	[thread overview]
Message-ID: <57129BB1.8020802@za3k.com> (raw)

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

Reproduction case after running into the same problem as Paride Legovini: http://article.gmane.org/gmane.comp.file-systems.btrfs/48706/match=send

To recap, the basic problem is that you can get into a state where "btrfs-send -c" fails for a subvolume, with "ERROR: parent determination failed for 9622".

I'm pretty sure this isn't the intended behavior, and it's certainly preventing me from copying my backups right now. If someone could confirm on a **completely** fresh system I'd appreciate it.

[root@burn ~]# sudo btrfs sub create m
Create subvolume './m'
[root@burn ~]# sudo btrfs sub create m/a
Create subvolume 'm/a'
[root@burn ~]# sudo btrfs sub create m/b
Create subvolume 'm/b'
[root@burn ~]# sudo btrfs sub snapshot m/a -r a
Create a readonly snapshot of 'm/a' in './a'
[root@burn ~]# sudo btrfs sub snapshot m/b -r b
Create a readonly snapshot of 'm/b' in './b'
[root@burn ~]# sudo btrfs sub delete m/a
Delete subvolume (no-commit): '/root/m/a'
[root@burn ~]# sudo btrfs sub delete m/b
Delete subvolume (no-commit): '/root/m/b'
[root@burn ~]# sudo btrfs sub delete m
Delete subvolume (no-commit): '/root/m'
[root@burn ~]# sudo btrfs send -c a b >/dev/null
At subvol b
ERROR: parent determination failed for 9622

[root@burn ~]# sudo btrfs subvolume show a
/root/a
        Name:                   a
        UUID:                   c86cbbb0-9dea-cf43-809d-637c57dc7e65
        Parent UUID:            bbad9a60-b418-3b46-93f5-84b8ac62adf6
        Received UUID:          -
        Creation time:          2016-02-19 08:31:47 -0800
        Subvolume ID:           9622
        Generation:             18121
        Gen at creation:        18121
        Parent ID:              5
        Top level ID:           5
        Flags:                  readonly
        Snapshot(s):

[root@burn ~]# sudo btrfs subvolume show b
/root/b
        Name:                   b
        UUID:                   bb9256c1-4fb4-ee4e-b072-0ee570521d06
        Parent UUID:            c5890f1a-94f0-ac48-a69d-656f8e0b7fc6
        Received UUID:          -
        Creation time:          2016-02-19 08:31:49 -0800
        Subvolume ID:           9623
        Generation:             18122
        Gen at creation:        18122
        Parent ID:              5
        Top level ID:           5
        Flags:                  readonly
        Snapshot(s):

[root@burn ~]# btrfs --version
btrfs-progs v4.4.1

[root@burn ~]# uname -a
Linux burn 4.5.0-1-ARCH #1 SMP PREEMPT Tue Mar 15 09:41:03 CET 2016 x86_64 GNU/Linux

---
Zachary Vance


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-04-16 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16 20:08 Zachary Vance [this message]
2016-04-17  3:37 ` btrfs-send -c fails: reproduction case Duncan

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=57129BB1.8020802@za3k.com \
    --to=za3k@za3k.com \
    --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 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).