From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Mathijs Kwik <mathijs@bluescreen303.nl>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Problems with incremental btrfs send (out of order instructions?)
Date: Thu, 01 Aug 2013 10:49:02 +0200 [thread overview]
Message-ID: <51FA20FE.7020708@giantdisaster.de> (raw)
In-Reply-To: <CAKvOHKD+cYp+CO4XLXkktnFZ_5n1tZnbrqS3D+T8nJhVEReWig@mail.gmail.com>
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.
[...]
> Can someone have a look at my dumpfile and confirm this is indeed a
> problem with btrfs send as opposed to something I am doing wrong?
According to your dumpfile, the file nixpkgs/pkgs/applications/version-management/subversion-1.2.x/default.nix needs to be there in the parent subvolume. Apparently it isn't. Since btrfs send enforces that sent snapshots are read-only, and btrfs receive sets received subvolumes to read-only immediately after the reception, it can't be your fault. It has to be the fault of the btrfs send logic.
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 :)
next prev parent reply other threads:[~2013-08-01 8:49 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 [this message]
2013-08-17 14:00 ` Xavier Bassery
2013-08-17 15:14 ` Mathijs Kwik
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=51FA20FE.7020708@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=mathijs@bluescreen303.nl \
/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.