Hello,

I have the Postgresql 10.2 database running on AIX Operating System and the database is created and stored on a distributed file-system.

There was a test operation which shuts down the file-system.

Soon after that, a coredump (abort) of Postgresql process was seen with the following stack :

IOT/Abort trap in raise at 0x90000000290e2ac
0x90000000290e2ac (raise+0x6c) e8410028             ld   r2,0x28(r1)
(dbx) t
raise(??) at 0x90000000290e2ac
abort() at 0x90000000292cc38
errfinish() at 0x10000b848
XLogWrite() at 0x1000d7170
XLogBackgroundFlush() at 0x1000e4aa4
WalWriterMain() at 0x100500fc8
AuxiliaryProcessMain() at 0x1004ce0ec
StartChildProcess() at 0x1000b7000
reaper() at 0x1000bbc6c
__fd_select(??, ??, ??, ??, ??) at 0x900000002a3400c
postmaster.do_start_bgworker.ServerLoop() at 0x1000b9220
PostmasterMain() at 0x1000bdb6c
main() at 0x1000006bc
(dbx)

From what i understand from the stack/code it indicates that a possible failure to write to the file-system caused Postgresql process to abort itself.

Could you please let me know if this kind of abort of Postgresql is expected when the file-system goes down ?

Or if i need to provide more information, let me know.

Thanks for the help in advance!

Regards,
Sangeeth Keeriyadath