Обсуждение: Page verification failed, calculated Checksum 1065 but expected 42487

Поиск
Список
Период
Сортировка

Page verification failed, calculated Checksum 1065 but expected 42487

От
Ramakrishna Reddy Nandyala
Дата:

Dear Team,

We are using pg12 with rhel8 and Cybertrust Transperent encryption (CTE) as encysution,recently we had faced a peculiar issue where all of sudden backup is getting failed with checksum validation failure for few objects. We have to truncate/restore the data from the backup in order to resume the backup and able to access the objects,
we would like to know is there any known issues with respect to  this combination of infra, any leads would be appreciated to understand the root cause of the issue.

Thank
Ramakrishna 

Re: Page verification failed, calculated Checksum 1065 but expected 42487

От
Tomas Vondra
Дата:
On 1/6/26 14:59, Ramakrishna Reddy Nandyala wrote:
> 
> Dear Team,
> 
> We are using pg12 with rhel8 and Cybertrust Transperent encryption (CTE)
> as encysution,

I'm not sure what "Cybertrust Transparent Encryption" is exactly. I've
only found "CipherTrust Transparent Encryption" from Thales, but I have
no idea if that's what you're using ...

> recently we had faced a peculiar issue where all of sudden
> backup is getting failed with checksum validation failure for few
> objects. We have to truncate/restore the data from the backup in order
> to resume the backup and able to access the objects,
> we would like to know is there any known issues with respect to  this
> combination of infra, any leads would be appreciated to understand the
> root cause of the issue.
> 

I'm afraid that's impossible to answer without much more information. So
many things in various layers could have caused this. It could be a
Postgres bug, or maybe it's something in the transparent encryption
system, or maybe it's a storage issue. Who knows?

I suggest you talk to authors of the encryption solution, and try to
figure it out with them. I suppose you're paying them for the solution
and support, and they are probably in the best position to help you.

But they'll need some information about the problem too, I guess. You
haven't even told us which Postgres version you're running, on what OS,
how much data is there, and so on.

What I usually do in data corruption cases is to look for "weird" things
since the last successful operation (before hitting the issue). It might
be a crash/recovery of the database, storage issues, unexpected reboot,
or any other thing that does not happen often. It's hard to re


regards

-- 
Tomas Vondra