BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM
Date
Msg-id 17937-c93266adaef384ff@postgresql.org
Whole thread Raw
Responses Re: BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM  (Joe Conway <mail@joeconway.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17937
Logged by:          Marc Morad
Email address:      marc.morad@gmail.com
PostgreSQL version: 13.8
Operating system:   Alma 8
Description:

This problem occured on PostgreSQL version 13.8 and 14.7. 

After we migrated the VM from CentOS 7 to AlmaLinux 8, we had a few issues
with broken/corrupt indexes. This problem occured a total of 3 times. Each
time the procedure of the migration was exactly the same. 
We are using a DRBD device to store our database redundantly, which we
reused when we migrated to AlmaLinux 8. 

The error messages all looked very similar to the following: 
Database error: [S]ERROR#012[V]ERROR#012[C]XX002#012[M]table tid from new
index tuple (3346213,70) cannot find insert offset between offsets 2 and 4
of block 5485 in index 

Have you ever heard of a similiar problem ?
Any leads what might cause these problems would be very helpful. 

Thank you and kind regards,
Marc


pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware)
Next
From: Peter Eisentraut
Date:
Subject: Re: AW: BUG #17923: Excessive warnings of collation version mismatch in logs