8 days looped? (btrfsck --repair --init-extent-tree)

[Martin <m_btrfs@ml1.co.uk>]

Dear list,

I've been trying to recover a 2TB single disk btrfs from a good few days
ago as already commented on the list. btrfsck complained of an error in
the extents and so I tried:

btrfsck --repair --init-extent-tree /dev/sdX


That was 8 days ago.

The btrfs process is still running at 100% cpu but with no disk activity
and no visible change in memory usage.

Looped?

Is there any way to check whether it is usefully doing anything or
whether this is a lost cause?


The only output it has given, within a few seconds of starting, is:


parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
Ignoring transid failure


Any comment/interest before abandoning?

This all started from trying to delete/repair a directory tree of a few
MBytes of files...


Regards,
Martin