Hi, On 2023/06/12 20:40, Bart Van Assche wrote:
Right on queue ... please find attached. Not seeing any content in any of the files from the tar czf so I doubt there is much use here ... perhaps you might be able to explain why all of these files under /sys/kernel/debug/block would be empty?On 6/9/23 00:29, Jaco Kroon wrote:I'm attaching dmesg -T and ps axf. dmesg in particular may provide clues as it provides a number of stack traces indicating stalling at IO time. Once this has triggered, even commands such as "lvs" goes into uninterruptable wait, I unfortunately didn't test "dmsetup ls" now and triggered a reboot already (system needs to be up).To me the call traces suggest that an I/O request got stuck. Unfortunately call traces are not sufficient to identify the root cause in case I/O gets stuck. Has debugfs been mounted? If so, how about dumping the contents of /sys/kernel/debug/block/ into a tar file after the lockup has been reproduced and sharing that information?tar -czf- -C /sys/kernel/debug/block . >block.tgz
Kind Regards, Jaco
Attachment:
block.tgz
Description: application/gzip
Attachment:
ps.txt.gz
Description: application/gzip
Attachment:
dmesg.txt.gz
Description: application/gzip
