btrfs scrub results in kernel oops does not proceed and cannot be canceled

[Sergio Callegari <sergio.callegari@gmail.com>]

Hi,

yesterday my laptop (kernel 6.10.13) froze coming out of hibernation. 
After that it will not boot anymore, saying that the root (that is on 
btrfs) cannot be mounted. I am dropped to an emergency shell and if I 
try to manually mount from there, I get level verify errors.

Tried to boot a live iso (with kernel 6.11.5) and to see what might be 
going on.

Managed to mount with -o rescue=ibadroots,ro getting transid errors.

- As soon as I start the scrub the kernel oopses.
- The scrub does not seem to progress (calling it with status).
- The scrub cannot be canceled.

The kernel oops appears scary. Even if my filesystem is corrupted the 
way in which these tools break rather than erroring out in a nicer way 
is not very helpful.

The plain btrfs check report a level error on one root and I think I do 
not have backup roots.

- is there a way to find out if the problem affects all subvolumes or a 
single one?
- is there a way to find out what can be trusted attempting a data 
recovery with the mount based on -o rescue=ibadroots,ro?

Is there any way to find out if my nvme (the hardware device) can be 
trusted to be used again (namely if the problem originated from the 
hardware of from an error in the kernel)? The fact that the problem 
appeared when using hibernation makes me thing that maybe the nvme is 
not at fault and that it was something else.

Any clue on what could be tried on my side? Why does the kernel end up 
in an oops?

Thanks,

Sergio