Hi,
More on my issue, I have "uncorrectable errors"
# btrfs scrub status /
scrub status for e11013b3-b244-4d1a-a9c7-3956db1a699c
scrub started at Thu Apr 23 19:07:45 2015 and finished after 372 seconds
total bytes scrubbed: 167.13GiB with 13 errors
error details: read=13
corrected errors: 0, uncorrectable errors: 13, unverified errors: 0
Before going to my backups, how can know the files impacted by those
uncorrectable errors?
Best regards,
--Martin
On 04/18/2015 09:45 AM, Martin Monperrus wrote:
> Dear Btrfs developers,
>
> For some unknown reasons, my BTRFS filesystem is corrupted. dmesg prints
>
> |BTRFS critical (device sda2): corrupt leaf, slot offset bad:
> block=43231330304,root=1, slot=47|
>
> (more than 1000x in the dmesg trace).
>
> btrfs check --repair fails with:
>
> read block failed check_tree_block
> incorrect offset 12725 2298746482
> items overlap, can't fix
> cmds_check.c:2918: fix_item_offset: Assertion 'ret' failed
>
> How to list the files in block #43231330304 affected by the corruption?
> How to repair block #43231330304?
>
> Best regards,
>
> --Martin
>
--
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
