From: Mathijs Kwik <mathijs@bluescreen303.nl>
To: Xavier Bassery <xavier@bartica.org>
Cc: Stefan Behrens <sbehrens@giantdisaster.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Problems with incremental btrfs send (out of order instructions?)
Date: Sat, 17 Aug 2013 17:14:36 +0200 [thread overview]
Message-ID: <87zjsg8i3n.fsf@bluescreen303.nl> (raw)
In-Reply-To: <b866582a35e6e829b88bdea3df8a57b0@bartica.org> (Xavier Bassery's message of "Sat, 17 Aug 2013 16:00:41 +0200")
Xavier Bassery <xavier@bartica.org> writes:
> On 2013-08-01 10:49, Stefan Behrens wrote:
>> On Wed, 31 Jul 2013 23:33:59 +0200, Mathijs Kwik wrote:
>>> Hi all,
>>>
>>> For some time, I've successfully deployed btrfs send/receive as a
>>> viable backup solution.
>>> It's fast and flexible and nicely scriptable =)
>>> However, every once in a while, trouble strikes on the receiving end
>>> with a message like:
>>>
>>> ERROR: rename
>>> nixpkgs/pkgs/applications/version-management/subversion-1.2.x/default.nix
>>> -> o2979-81788-0 failed. No such file or directory
>>
>> I've also seen such an errors. It's an error in the send code.
>>
> [...]
>> If you enter a bug on bugzilla.kernel.org (refer to
>>
>> <https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#How_do_I_report_bugs_and_issues.3F>),
>> you increase the probability that somebody fixes the issue some day
>> :)
>
>
> This bug has been reported in BZ #60673 [1] and was fixed in Josef's
> btrfs-next commit
> titled "Btrfs: check our parent dir when doing a compare send" [2].
> This fix hasn't been merged in the stable kernel yet.
>
> Thanks to all.
I have been using the patch for 10 days now, and it's a huge
improvement, but we're not out of the woods yet it seems :(
https://bugzilla.kernel.org/show_bug.cgi?id=60673
>
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=60673
> [2]
> http://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/fs/btrfs/send.c?id=441f6d6f7115a927f3e13f7acc53184a6081dbe0
prev parent reply other threads:[~2013-08-17 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 21:33 Problems with incremental btrfs send (out of order instructions?) Mathijs Kwik
2013-08-01 8:49 ` Stefan Behrens
2013-08-17 14:00 ` Xavier Bassery
2013-08-17 15:14 ` Mathijs Kwik [this message]
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=87zjsg8i3n.fsf@bluescreen303.nl \
--to=mathijs@bluescreen303.nl \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=xavier@bartica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.