Re: corrupt files
On Thu, 26 Feb 2015 11:24:51 -0500 (EST), Wietse Venema stated: Postfix User: FreeBSD-10.1 amd64 I recently had a power outage that resulted in a system shutdown. When I rebooted the system, postfix elicited this massage: postfix/postfix-script: warning: damaged message: corrupt/3ktB2X6JxNz3DljZ postfix/postfix-script: warning: damaged message: corrupt/3ktG0Z1PCPz3DlXm When Postfix doesn't find the expected information in a queue file, it saves the message in the corrupt directory. This happens only with messages that were already accepted into the queue (and deleted from the sender's queue or from the maildrop queue), not with messages that were still in transit. I am wondering how to remove these files. I tried using postsuper -d ALL but that failed. I even tried giving it the ID number but it still did not delete the files. Is it okay to delete them manually? The files are not part of the mail queue, and you can therefore delete them without affecting how Postfix works. Depending on the kind of damage the postcat command may be able to save the sender/recipient informantion and some of the content. Wietse Thank you. The files were 0 length, so I just deleted them. -rwx-- 1 postfix wheel 0B 2015-02-26 06:04:05 EST 3ktB2X6JxNz3DljZ* -rwx-- 1 postfix wheel 0B 2015-02-26 09:02:41 EST 3ktG0Z1PCPz3DlXm* -- Jerry
Re: corrupt files
Postfix User: FreeBSD-10.1 amd64 I recently had a power outage that resulted in a system shutdown. When I rebooted the system, postfix elicited this massage: postfix/postfix-script: warning: damaged message: corrupt/3ktB2X6JxNz3DljZ postfix/postfix-script: warning: damaged message: corrupt/3ktG0Z1PCPz3DlXm When Postfix doesn't find the expected information in a queue file, it saves the message in the corrupt directory. This happens only with messages that were already accepted into the queue (and deleted from the sender's queue or from the maildrop queue), not with messages that were still in transit. I am wondering how to remove these files. I tried using postsuper -d ALL but that failed. I even tried giving it the ID number but it still did not delete the files. Is it okay to delete them manually? The files are not part of the mail queue, and you can therefore delete them without affecting how Postfix works. Depending on the kind of damage the postcat command may be able to save the sender/recipient informantion and some of the content. Wietse
Re: corrupt files
Postfix User: Thank you. The files were 0 length, so I just deleted them. -rwx-- 1 postfix wheel 0B 2015-02-26 06:04:05 EST 3ktB2X6JxNz3DljZ* -rwx-- 1 postfix wheel 0B 2015-02-26 09:02:41 EST 3ktG0Z1PCPz3DlXm* Did you have multiple power failures, one at 06:04 and one at 09:02? Postfix sets the execute bit and fsync()s the file. Only after fsync() returns successfully Postfix sends a I've got the message reply to the sender, so that the sender can delete its copy. The above output suggests a system crash before fsync() completed. But these files have time stamps spaced three hours apart. Did you have multiple power failures? Wietse
Re: corrupt files
On Thu, 26 Feb 2015 12:48:42 -0500 (EST), Wietse Venema stated: Postfix User: Thank you. The files were 0 length, so I just deleted them. -rwx-- 1 postfix wheel 0B 2015-02-26 06:04:05 EST 3ktB2X6JxNz3DljZ* -rwx-- 1 postfix wheel 0B 2015-02-26 09:02:41 EST 3ktG0Z1PCPz3DlXm* Did you have multiple power failures, one at 06:04 and one at 09:02? Postfix sets the execute bit and fsync()s the file. Only after fsync() returns successfully Postfix sends a I've got the message reply to the sender, so that the sender can delete its copy. The above output suggests a system crash before fsync() completed. But these files have time stamps spaced three hours apart. Did you have multiple power failures? Wietse Yes, I did. The UPS apparently never kicked in. I have always had problems getting them to work on a FreeBSD system. One of these days I hope to get it working correctly. -- Jerry
Re: corrupt files
Wietse: But these files have time stamps spaced three hours apart. Did you have multiple power failures? Postfix User: Yes, I did. The UPS apparently never kicked in. I have always had problems getting them to work on a FreeBSD system. One of these days I hope to get it working correctly. Thanks for the clarification. This explains the zero-length executable files with different time stamps. As for FreeBSD and UPSes, I have run FreeBSD for 18+ years backed up by a variety of UPSes, and all UPSes that I have used would take over as soon as power drops (or as soon as I yanked the power chord for testing). The only time this did not work was when I had plugged the computer into an UPS outlet that had surge protection only, no power backup. Wietse
