Am Mi., 17. März 2021 um 02:54 Uhr schrieb Dāvis Mosāns :
> > root@hikitty:~$ install/btrfs-progs-5.9/btrfs check --readonly /dev/sdi1
> > Opening filesystem to check...
> > checksum verify failed on 99593231630336 found 00B6 wanted
> > checksum verify failed on 124762809384960 found
Am Mi., 17. März 2021 um 03:59 Uhr schrieb Chris Murphy
:
>
> On Tue, Mar 16, 2021 at 7:39 PM Qu Wenruo wrote:
> > > Using that restore I was able to restore approx. 7 TB of the
> > > originally stored 22 TB under that directory.
> > > Unfortunately nearly all the files are damaged. Small text fil
Hi again.
> Looks like the answer is no. The chunk tree really has to be correct
> first before anything else because it's central to doing all the
> logical to physical address translation. And if it's busted and can't
> be repaired then nothing else is likely to work or be repairable. It's
> tha
> > Would it make sense to just try restore -t on any root I got with
> > btrfs-find-root with all of the snapshots?
>
> Yes but I think you've tried this and you only got corrupt files or
> files with holes, so that suggests very recent roots are just bad due
> to the corruption, and older ones a
> > > I don't know. The exact nature of the damage of a failing controller
> > > is adding a significant unknown component to it. If it was just a
> > > matter of not writing anything at all, then there'd be no problem. But
> > > it sounds like it wrote spurious or corrupt data, possibly into
> > >
> I don't know. The exact nature of the damage of a failing controller
> is adding a significant unknown component to it. If it was just a
> matter of not writing anything at all, then there'd be no problem. But
> it sounds like it wrote spurious or corrupt data, possibly into
> locations that were
> > I think you best chance is to start out trying to restore from a
> > recent snapshot. As long as the failed controller wasn't writing
> > totally spurious data in random locations, that snapshot should be
> > intact.
>
> i.e. the strategy for this is btrfs restore -r option
>
> That only takes
ess damaged?
So far I ran no btrfs check --repair.
Since the original and the backup have been damaged any help would be
highly appreciated.
Thanks for your assistance.
Kind regards,
Sebastian Roller
Attachment. All outputs. ---
uname -a
Linux hikitty 5.7.7-1.el7.e
