From: Miao Xie <miaox@cn.fujitsu.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Josef Bacik <jbacik@fusionio.com>
Subject: Re: problems with btrfs send / restore
Date: Mon, 15 Oct 2012 18:16:04 +0800 [thread overview]
Message-ID: <507BE264.1060500@cn.fujitsu.com> (raw)
In-Reply-To: <50772408.9040303@profihost.ag>
On thu, 11 Oct 2012 21:54:48 +0200, Stefan Priebe wrote:
> Am 11.10.2012 21:43, schrieb David Sterba:
>> On Thu, Oct 11, 2012 at 09:33:54PM +0200, Stefan Priebe wrote:
>>> [server: /btrfs/target]# btrfs send -i /btrfs/src/\@snapshot/1
>>> /btrfs/src/\@snapshot/2 | btrfs receive /btrfs/target/\@snapshot/
>>> At subvol /btrfs/src/@snapshot/2
>>> At subvol 2
>>> ERROR: failed to open /btrfs/target/@snapshot/@snapshot/1/test.tar. No such file or directory
>> ^^^^^^^^^^^^^^^^^^^
>>
>> I wonder if this is the ghost snapshot dir entry that Miao fixed. Did
>> somehow get into the 'send' stream and confused the receive side.
>>
>> david
>
> i missed two facts:
> 1.) vanilla kernel 3.6.1
> 2.) latest btrfs tools git (cloned at 10/10/2012)
Sorry, I can not reproduce this problem, could you send me the detailed steps?
Thanks
Miao
>
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-10-15 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 19:33 problems with btrfs send / restore Stefan Priebe
2012-10-11 19:43 ` David Sterba
2012-10-11 19:54 ` Stefan Priebe
2012-10-15 10:16 ` Miao Xie [this message]
2012-10-15 19:21 ` Stefan Priebe
2012-10-15 19:42 ` Alex Lyakas
2012-10-15 20:06 ` Stefan Priebe
2012-10-15 20:14 ` Alex Lyakas
2012-10-16 14:16 ` Stefan Priebe - Profihost AG
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=507BE264.1060500@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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).