Hi Bart, Thank you for you patience for this ...Please find attached updated ps and dmesg too, diskinfo wasn't regenerated but this doesn't generally change.
Not sure how this all works, according to what I can see the only disk with pending activity (queued) is sdw? Yet, a large number of processes is blocking on IO, and yet again the stack traces in dmesg points at __schedule. For a change we do not have lvcreate in the process list! This time that particular script's got a fsck in uninterruptable wait ...
Kind regards, Jaco On 2023/06/19 01:56, Bart Van Assche wrote:
On 6/18/23 12:34, Jaco Kroon wrote: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?tar -czf- -C /sys/kernel/debug/block . >block.tgzApparently the tar command is incompatible with debugfs :-( I should have tested the command before I sent it to you.Does this work better? (cd /sys/kernel/debug/block/ && grep -r . .) | gzip -9 > block.gz Thanks, Bart.
Attachment:
disksetup.txt.gz
Description: application/gzip
Attachment:
ps.txt.gz
Description: application/gzip
Attachment:
dmesg.txt.gz
Description: application/gzip
Attachment:
block.gz
Description: application/gzip
