From: Alex Lyakas <alex.btrfs@zadarastorage.com>
To: Stefan Priebe <s.priebe@profihost.ag>
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 21:42:54 +0200 [thread overview]
Message-ID: <CAOcd+r2sZYxxNRQS2h-LY9Fpd791JRKiVq2gT-xBpkPY8=FsQQ@mail.gmail.com> (raw)
In-Reply-To: <507C6239.1030208@profihost.ag>
Hi Stefan,
Is /btrfs/target/\@snapshot/ a subvolume or a 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).
Thanks,
Alex.
On Mon, Oct 15, 2012 at 9:21 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> Am 15.10.2012 12:16, schrieb Miao Xie:
>
>> 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?
>
>
> mhm there is nothing special. But i try to provide more information / a
> small howto:
>
> # mount |grep btrfs
> /dev/sdb on /btrfs/src type btrfs (rw)
> /dev/sdc on /btrfs/target type btrfs (rw)
>
> # btrfs subvolume list /btrfs/target/
> # btrfs subvolume list /btrfs/src/
> ID 277 top level 5 path @snapshot/1
> ID 278 top level 5 path @snapshot/2
> ID 288 top level 5 path @snapshot/3
>
> # btrfs send /btrfs/src/\@snapshot/1 | btrfs receive
> /btrfs/target/\@snapshot/
> At subvol /btrfs/src/@snapshot/1
> At subvol 1
> #
>
> Now i was trying to send an incremental snapshot:
>
> # 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
> #
>
> Greets,
>
> 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 19:42 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 [this message]
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='CAOcd+r2sZYxxNRQS2h-LY9Fpd791JRKiVq2gT-xBpkPY8=FsQQ@mail.gmail.com' \
--to=alex.btrfs@zadarastorage.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--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).