Re: Computer stalled, apparently from filesystem corruption

[Pierre Abbat <phma@bezitopo.org>]

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Friday, March 11, 2022 9:48:35 PM EDT Zygo Blaxell wrote:
> There's no indication of corruption in those logs.  Above the kernel
> is complaining that it's taking too long to finish transactions, which
> could be a btrfs problem, or a hardware problem, or even simply a large
> filesystem running normally on very slow disks.  Not enough information
> to tell.

It couldn't be a very slow disk, because all the drives are NVM or SSD.

> When posting logs, extract all lines with 'btrfs' on them, plus context
> lines, e.g.
> 
> 	grep -B9 -i btrfs /var/log/kern.log
> 
> or
> 
> 	dmesg | grep -B9 -i btrfs
> 
> If you can reproduce the hang, enable sysrq and do Alt-SysRq-W when it
> hangs (or run
> 
> 	echo w > /proc/sysrq-trigger
> 
> from a command line).  This will provide stack traces of all blocked
> processes so we can see what the transaction is waiting for.

Here are the whole sections of the logfiles from the first error until the 
computer hung, compressed. I'm afraid to run the rsync script again because it 
might hang the computer. Is there a way to find out if the filesystem access 
hung on a bad sector or something?

Pierre

-- 
Lanthanidia deliciosa: What the kiwifruit would be
if it weren't so radioactive.

[-- Attachment #2: syslog-excerpts.bz2 --]
[-- Type: application/x-bzip, Size: 6840 bytes --]