From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: "linux-btrfs@vger.kernel.org Btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send in 3.12 : can't find snapshot?
Date: Tue, 17 Dec 2013 19:51:41 +0800 [thread overview]
Message-ID: <52B03ACD.1080000@cn.fujitsu.com> (raw)
In-Reply-To: <87ppowqn9g.fsf@maru2.md5i.com>
Hello Michael,
I sent a patch to fix the issue(cc you already), can you have a try
and see if it fix your problem.
Thanks,
Wang
On 12/17/2013 09:28 AM, Michael Welsh Duggan wrote:
> Wang Shilong <wangshilong1991@gmail.com> writes:
>
>> Hello Michael,
>>
>>> I built the new btrfs-progs 3.12 recently. I note that the version
>>> information doesn't seem to match this:
>>>
>>> # ./btrfs --version
>>> Btrfs v0.20-rc1-358-g194aa4a
>>>
>>> Regardless, I was trying to use btrfs send (which worked in the older
>>> btrfs), and failed. Here's an example:
>>>
>>> # ./btrfs send -vvv -p /snapshots/bo /snapshots/bp > /dev/null
>>> At subvol /snapshots/bp
>>> ERROR: open @/snapshots/bp failed. No such file or directory
>>>
>>> Any idea what might be going on here?
>>>
>>> Here's the volume information:
>>>
>>> # ./btrfs sub show /
>>> /
>>> Name: @
>>> uuid: e5e505d6-1309-8447-b51e-73f08c9401d1
>>> Parent uuid: 156f93b9-1175-dc42-a1ee-65c00c5dcc2a
>>> Creation time: 2013-07-17 20:44:46
>>> Object ID: 259
>>> Generation (Gen): 296321
>>> Gen at creation: 20
>>> Parent: 5
>>> Top Level: 5
>>> Flags: -
>>> Snapshot(s):
>>> snapshots/bo
>>> snapshots/bp
>>>
>>> Kernel information:
>> Here it seemed that you changed your default sub-volume.(259 not 5)
>> I sent a patch before to fix this problem, it has not been pushed into
>> chris's master branch, patch url is:
>>
>> https://patchwork.kernel.org/patch/3258971/
>>
>> But is has been pushed into david's latest integration branch , you
>> can pull from:
>>
>> git pull http://github.com/kdave/btrfs-progs.git integration-20131211
> After compiling this version the above tests works. Now, however, the
> receive fails:
>
> # ./btrfs send -p /snapshots/bo /snapshots/bp | ./btrfs receive /backup/snapshots/root/
> At subvol /snapshots/bp
> At snapshot bp
> ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
> ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 48f0ebae83fd32f1, UUID_KEY, 90139d8200afeaab) ret=-1, error: No such file or directory
> ERROR: could not find parent subvolume
>
> More volume information:
>
> # ./btrfs sub show /backup/snapshots/root/bo
> /backup/snapshots/root/bo
> Name: bo
> uuid: 5e15ef24-f2d0-194f-886d-3f7afc7413a4
> Parent uuid: 9a226af3-8497-744b-90f7-d7e54d58946d
> Creation time: 2013-12-13 17:51:57
> Object ID: 1030
> Generation (Gen): 1046
> Gen at creation: 1042
> Parent: 5
> Top Level: 5
> Flags: readonly
> Snapshot(s):
> # ./btrfs sub show /snapshots/bo
> /snapshots/bo
> Name: bo
> uuid: f132fd83-aeeb-f048-abea-af00829d1390
> Parent uuid: e5e505d6-1309-8447-b51e-73f08c9401d1
> Creation time: 2013-12-13 17:50:15
> Object ID: 404
> Generation (Gen): 296977
> Gen at creation: 291623
> Parent: 259
> Top Level: 259
> Flags: readonly
> Snapshot(s):
> # ./btrfs sub show /snapshots/bp
> /snapshots/bp
> Name: bp
> uuid: 6f73d3f2-5f9b-4944-b2d2-3003331b2d10
> Parent uuid: e5e505d6-1309-8447-b51e-73f08c9401d1
> Creation time: 2013-12-15 22:24:57
> Object ID: 405
> Generation (Gen): 296977
> Gen at creation: 296301
> Parent: 259
> Top Level: 259
> Flags: readonly
> Snapshot(s):
>
>
next prev parent reply other threads:[~2013-12-17 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 3:40 btrfs send in 3.12 : can't find snapshot? Michael Welsh Duggan
2013-12-16 6:18 ` Wang Shilong
2013-12-17 1:28 ` Michael Welsh Duggan
2013-12-17 2:16 ` Wang Shilong
2013-12-17 11:51 ` Wang Shilong [this message]
2013-12-16 10:34 ` 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=52B03ACD.1080000@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mwd@md5i.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 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).