From: Stefan Priebe <s.priebe@profihost.ag>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: miaox@cn.fujitsu.com,
"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 22:06:32 +0200 [thread overview]
Message-ID: <507C6CC8.9060100@profihost.ag> (raw)
In-Reply-To: <CAOcd+r2sZYxxNRQS2h-LY9Fpd791JRKiVq2gT-xBpkPY8=FsQQ@mail.gmail.com>
Am 15.10.2012 21:42, schrieb Alex Lyakas:
> Is /btrfs/target/\@snapshot/ a subvolume or a directory?
A simple directory.
> can you pls try the patch that I posted here:
> http://www.spinics.net/lists/linux-btrfs/msg19583.html
>
> I feel that you're hitting a similar issue here. Before you apply the
> patch, please verify that you have /etc/mtab on your system (I will
> make a more formal patch later).
With your patch it works FINE!! Great!
Another problem i'm seeing is:
# btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs
receive /btrfs/target/\@snapshot/
At subvol /btrfs/src/@snapshot/2
ERROR: Failed to lookup path for root 0 - No such file or directory
ERROR: unable to resolve path for root 350
Then i have to wait some seconds and the same command works fine. I see
the same with btrfs subvolume list PATH
and it is unrelated to your patch.
Stefan
next prev parent reply other threads:[~2012-10-15 20:06 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
2012-10-15 19:21 ` Stefan Priebe
2012-10-15 19:42 ` Alex Lyakas
2012-10-15 20:06 ` Stefan Priebe [this message]
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=507C6CC8.9060100@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=alex.btrfs@zadarastorage.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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).