btrfs send error

btrfs send error

[Pavol Cupka]

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?

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

Re: btrfs send error

[Filipe Manana]

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."

Re: btrfs send error

[Pavol Cupka]

Will do.
Thank you.


On Wed, Feb 17, 2016 at 3:01 PM, Filipe Manana <fdmanana@gmail.com> wrote:
> 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."

Re: btrfs send error

[Duncan]

Filipe Manana posted on Wed, 17 Feb 2016 14:01:15 +0000 as excerpted:

> 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

Has that patch been earmarked for stable, and stable just hasn't caught 
up to it yet?

Because the OP is on 4.1-LTS, which is definitely still within the 
reasonable support window and being an LTS, should still be supported.

If it's already earmarked for stable and simply hasn't made it into a 
stable release yet, that's understandable, tho having it specifically 
stated, thus making waiting for it to hit stable an option, would be 
nice. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman