Strange failures on chipmunk - Mailing list pgsql-hackers

From Thomas Munro
Subject Strange failures on chipmunk
Date
Msg-id CA+hUKGJb7aFwnNY64W9g3WxpsLDS3EkePja7COOd3wKd2W-D4g@mail.gmail.com
Whole thread Raw
Responses Re: Strange failures on chipmunk
List pgsql-hackers
Hi,

chipmunk (an armv6l-powered original Raspberry Pi model 1?) has failed
in a couple of weird ways recently on 14 and master.

On 14 I see what appears to be a corrupted log file name:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2022-06-16%2006%3A48%3A07

cp: cannot stat

\342\200\230/home/pgbfarm/buildroot/REL_14_STABLE/pgsql.build/src/test/recovery/tmp_check/t_002_archiving_primary_data/archives/000000010000000000000003\342\200\231:
No such file or directory

On master, you can ignore this failure, because it was addressed by 93759c66:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2022-05-11%2015%3A26%3A01

Then there's this one-off, that smells like WAL corruption:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2022-06-13%2015%3A12%3A44

2022-06-13 23:02:06.988 EEST [30121:5] LOG:  incorrect resource
manager data checksum in record at 0/79B4FE0

Hmmm.  I suppose it's remotely possible that Linux/armv6l ext4 suffers
from concurrency bugs like Linux/sparc.  In that particular kernel
bug's case it's zeroes, so I guess it'd be easier to speculate about
if the log message included the checksum when it fails like that...



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PATCH] minor reloption regression tests improvement
Next
From: Matthias van de Meent
Date:
Subject: Re: making relfilenodes 56 bits