From: Zachary Vance <vanceza@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: [resend] btrfs-send -c fails: reproduction case
Date: Sun, 17 Apr 2016 14:55:20 -0700 [thread overview]
Message-ID: <CAC8+__7+ALM5WK-+aCkH0Nc1GUTV5v=7R0SB9LFFE48YM3NLeg@mail.gmail.com> (raw)
Apologies for the repeat send for anyone that gets this twice; I was
informed there was a problem with my mail setup and many ISPs would
block the first message. I have also simplified the reproduction case.
---
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". It appears the problem happens when
the 'parent_uuid' does not exist.
I'm pretty sure this isn't the intended behavior, and it's certainly
preventing me from copying my backups right now.
burn% sudo btrfs subvol create a
Create subvolume './a'
burn% sudo btrfs subvol snapshot a -r a-r
Create a readonly snapshot of 'a' in './a-r'
burn% sudo btrfs subvol create b1
Create subvolume './b1'
burn% sudo btrfs subvol snapshot b1 -r b2
Create a readonly snapshot of 'b1' in './b2'
burn% sudo btrfs subvol del b1
Delete subvolume (no-commit): '/data/b1'
burn% sudo btrfs send -c b2 a-r >/dev/null
At subvol a-r
ERROR: parent determination failed for 9637
/data/a-r
Name: a-r
UUID: 819415e9-ea57-4a4d-9745-78a65f19b614
Parent UUID: e63b985a-3463-be4c-8ad5-900cd147ef7d
Received UUID: -
Creation time: 2016-02-20 10:19:59 -0800
Subvolume ID: 9638
Generation: 18524
Gen at creation: 18524
Parent ID: 5
Top level ID: 5
Flags: readonly
Snapshot(s):
burn% sudo btrfs subvolume show b2
/data/b2
Name: b2
UUID: e1d0314d-9c2a-5240-9f4c-1716b7e87741
Parent UUID: 00920504-c78b-ee42-af9f-05f4600321bb
Received UUID: -
Creation time: 2016-02-20 10:19:01 -0800
Subvolume ID: 9637
Generation: 18522
Gen at creation: 18522
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
next reply other threads:[~2016-04-17 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 21:55 Zachary Vance [this message]
2016-04-17 22:36 ` [resend] btrfs-send -c fails: reproduction case Chris Murphy
2016-04-18 1:46 ` Zachary Vance
2016-04-18 20:52 ` Henk Slager
2016-04-19 8:15 ` 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='CAC8+__7+ALM5WK-+aCkH0Nc1GUTV5v=7R0SB9LFFE48YM3NLeg@mail.gmail.com' \
--to=vanceza@gmail.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).