Spielereien
Kanu
Geopolitik
Business
TopoDB
POI
Klettersteigen
History
TransPool
Thermal Baden
Brokenstuben
Goldwaschen
Blog
Contact
/ home / computer / postgresql / .
PostgreSQL 17.6
During our investigation, our infrastructure team identified what appears to be an NVMe storage issue on the Azure VM. The kernel logs show repeated NVMe controller resets followed by multiple read I/O errors across several NVMe devices:
kernel: nvme: resetting controller due to persistent internal error
kernel: Read ... Host Aborted Command
kernel: I/O error, dev nvme..., op:(READ)
The PostgreSQL error occurred around the same timeframe, which makes us suspect the underlying storage issue may have caused the WAL flush failure:
LOG: request to flush past end of generated WAL; request 5D116/1, current position C8F/734E66C0
CONTEXT: writing block 4400857 of relation base/16384/1255337
ERROR: xlog flush request 5D116/1 is not satisfied --- flushed only to C8F/734E66C0
CONTEXT: writing block 4400857 of relation base/16384/1255337