From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
Subject: | Strange failures on chipmunk |
Date: | 2022-06-29 22:07:18 |
Message-ID: | CA+hUKGJb7aFwnNY64W9g3WxpsLDS3EkePja7COOd3wKd2W-D4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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...
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2022-06-29 22:12:46 | Re: making relfilenodes 56 bits |
Previous Message | Jacob Champion | 2022-06-29 21:38:48 | Re: [PATCH] minor reloption regression tests improvement |