From: Chris Mason <clm@fb.com>
To: David Arendt <admin@prnet.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send and kernel 3.17
Date: Mon, 6 Oct 2014 15:06:18 -0400 [thread overview]
Message-ID: <1412622378.31886.3@mail.thefacebook.com> (raw)
In-Reply-To: <5432E466.9070604@prnet.org>
On Mon, Oct 6, 2014 at 2:50 PM, David Arendt <admin@prnet.org> wrote:
> Hi,
>
> After upgrading to kernel 3.17 btrfs send has stopped working.
>
> ERROR: send ioctl failed with -5: Input/output error
>
> The following message is printed by kernel:
>
> [75322.782197] BTRFS error (device sda2): did not find backref in
> send_root. inode=461, offset=0, disk_byte=1094713344 found
> extent=1094713344
>
> btrfs inspect-internal inode-resolve -v 461 /u00/root.snapshot
> returns:
>
> /var/log/emerge-fetch.log
>
> After removing this file, the error moves on to another file.
>
> btrfs scrub output:
>
> scrub status for bc31b068-2c36-4ff2-ac5c-7ce55af5371d
> scrub started at Mon Oct 6 19:49:25 2014 and finished after 1748
> seconds
> total bytes scrubbed: 94.21GiB with 0 errors
>
> Other then the btrfs send problem, the filesystem works normally.
>
> Is this a bug in btrfs-send or is my filesystem corrupted and should
> be
> restored from backup ?
>
> Please tell me if I can do anything else to help debugging this issue.
Which kernel did you upgrade from? I don't think we have changes in
3.17 that should impact this.
Is merge-fetch.log just a simple append-only log file?
-chris
next prev parent reply other threads:[~2014-10-06 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 18:50 btrfs send and kernel 3.17 David Arendt
2014-10-06 19:06 ` Chris Mason [this message]
2014-10-06 19:48 ` David Arendt
2014-10-06 20:51 ` David Arendt
2014-10-06 22:22 ` Chris Mason
[not found] <DC336054-F307-4A86-AD6D-204E700DE9AA@prnet.org>
2014-10-07 13:19 ` Chris Mason
2014-10-07 20:45 ` David Arendt
2014-10-07 20:46 ` Chris Mason
2014-10-12 11:11 ` David Arendt
2014-10-12 15:24 ` john terragon
2014-10-12 21:35 ` David Arendt
2014-10-13 4:11 ` David Arendt
2014-10-13 12:40 ` john terragon
2014-10-13 15:40 ` David Arendt
2014-10-13 17:22 ` Rich Freeman
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=1412622378.31886.3@mail.thefacebook.com \
--to=clm@fb.com \
--cc=admin@prnet.org \
--cc=linux-btrfs@vger.kernel.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 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).