From: Filipe Manana <fdmanana@gmail.com>
To: Pavol Cupka <pavol.cupka@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send error
Date: Wed, 17 Feb 2016 14:01:15 +0000 [thread overview]
Message-ID: <CAL3q7H6XnesHaU1COssFnvdnkxZwAD+isPLcYXxeip1b4UULug@mail.gmail.com> (raw)
In-Reply-To: <CAH4oapcJVfd74Wg64+4Q+xXzF07U1NKrQTnhoOA1ry2sJogkXQ@mail.gmail.com>
On Wed, Feb 17, 2016 at 1:02 PM, Pavol Cupka <pavol.cupka@gmail.com> wrote:
> Hi all,
>
> when trying to btrfs send a snaphost I get this in dmesg:
> [8614395.539466] BTRFS error (device sda1): did not find backref in
> send_root. inode=673755, offset=131072, disk_byte=25730310144 found
> extent=25730310144
>
> scrub reveals no errors
> scrub status for bb8094e8-a7b1-4c2d-854e-77a9921e6f7e
> scrub started at Wed Feb 17 08:14:32 2016 and finished after 00:15:58
> total bytes scrubbed: 67.49GiB with 0 errors
>
> Is there something else that I might try to get this work?
Just upgrade to a 4.3 or 4.4 kernel, or build a kernel with the patch below.
The fix for this landed in 4.3:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d6589101b67a55107652050dfbf414403a93e351
>
> uname -a
> Linux 4.1.7-hardened-r1 #4 SMP Mon Nov 9 20:02:04 CET 2015 x86_64
> Intel(R) Atom(TM) CPU N2800 @ 1.86GHz GenuineIntel GNU/Linux
>
> btrfs --version
> btrfs-progs v4.3.1
>
> Thanks Pavol
> --
> 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
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2016-02-17 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 13:02 btrfs send error Pavol Cupka
2016-02-17 14:01 ` Filipe Manana [this message]
2016-02-17 14:17 ` Pavol Cupka
2016-02-18 10:02 ` Duncan
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=CAL3q7H6XnesHaU1COssFnvdnkxZwAD+isPLcYXxeip1b4UULug@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pavol.cupka@gmail.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).