On 30/3/2022 4:20 μ.μ., Wietse Venema wrote:
- The message was moved to the HOLD queue. It would still show up
with the "mailq" command.

Thank you Wietse,

I actually used postqueue -p to list queue, but I could not identify any of the un mail.

- The message was written to the incoming queue, but your file
system is corrupted. Stop Postfix, umount the file system, and keep
running FSCK (or whatever y9our OS calls it) until there are no
more repairs.

Are you using block-level device mirroring?

This is a VM hosted by our VPS provider (using KVM technology, as I remember), about which few details are provided here:

https://grnet.gr/en/services/computing-and-storage-services/vima/

Could the problem be isolated to our VM's OS (CentOS 7) and be handled by the Guest OS's tools or it could be attributed to the hosting storage array and/or hypervisor cluster? In other words could a corruption exist in the Virtual File System in the Guest OS or it could be caused by a the hypervisor environment?

In the meantime, I have identified more mails that users considered delivered successfully, but there is no sign of them in the logs; we should conclude that these mails were in fact not sent/received at all?

Thank you for your kind assistance,
Nick

Reply via email to