> How can I attempt to rebuild the metadata, with a treescan or
> otherwise?
I don't know unfortunately for backrefs.
>> In general metadata in Btrfs is fairly intricate and metadata
>> block loss is pretty fatal, that's why metadata should most
>> times be redundant as in 'dup' or 'raid1' or
On 2017-03-17 15:25, John Marrett wrote:
Peter,
Bad news. That means that probably the disk is damaged and
further issues may happen.
This system has a long history, I have had a dual drive failure in the
past, I managed to recover from that with ddrescue. I've subsequently
copied the
Peter,
> Bad news. That means that probably the disk is damaged and
> further issues may happen.
This system has a long history, I have had a dual drive failure in the
past, I managed to recover from that with ddrescue. I've subsequently
copied the contents of the drives to new disks and
> Read error at byte 0, while reading 3975 bytes: Input/output error
Bad news. That means that probably the disk is damaged and
further issues may happen.
> corrected errors: 0, uncorrectable errors: 2, unverified errors: 0
Even worse news.
> Incorrect local backref count on
I have a filesystem with uncorrectable errors in metadata. In the past
when I've experienced corruption due to drive failures it affected the
data and not metadata. I was able to delete the files and restored
their content from backup. Unfortunately I can't do this this time as
I have no way to
