non-data FIS,
non-CRC
On 04/24/2015 07:44 PM, Martin Monperrus wrote:
> Hi Duncan,
>
>> The kernel log (dmesg, also logged to syslog/journald on most systems)
>> from during the scrub should capture more information on those errors.
> Thanks. The dmesg log indeed contains t
c a0 00 00 08 00
[ 7695.814208] end_request: I/O error, dev sda, sector 20224
[ 7695.814222] ata1: EH complete
[ 7695.814227] BTRFS: unable to fixup (regular) error at logical
167135232000 on dev /dev/sda2
On 04/23/2015 08:05 PM, Martin Monperrus wrote:
> Hi,
>
> More on my issue, I h
s: 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 unknow
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_b
