On Thu, Feb 18, 2016 at 9:29 AM, Jan Alexander Steffens
<jan.steff...@gmail.com> wrote:
> Greetings,
>
> I'm getting reproducible Oopses when attempting "btrfs send" on my
> root vol, quickly ending in a hard lockup of the machine. Both
> incremental send and non-incremental send crash, the former much
> earlier. The volume is in a LUKS container.
>
> The initial fault is always during LZO decompression, but scrub does
> not find any errors. Could this be invalid compressed data with good
> checksums? "btrfs check" finds bad extent backrefs which --repair
> claims to fix, but they reappear on a subsequent check.
>
> Is there a way to find out which files' extents are damaged so I can
> delete them and complete my backup?
man btrfs-send
-v
Enable verbose debug output. Each occurrence of this option
increases the verbose level more.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
