GWMTA: Insufficient disk space

Source:  GroupWise Message Transfer Agent.

Explanation:  The MTA does not have sufficient disk space to write files into its input queues or holding queues. The MTA requires at least 1 MB of free disk space to run.

Possible Cause:  One or more locations are closed, resulting in a backlog of messages in the MTA holding queues in the directory.

Action:  Resolve the problems with the closed facilities so that normal message flow resumes. See "MTA Status Box Shows a Closed Location" in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems.

Possible Cause:  Other programs running the same server with the MTA have used up all available disk space.

Action:  Free up disk space so the MTA can continue processing messages. Check the MTA log file to see which queue the MTA can no longer write to so you know where more disk space is required. See "Using MTA Log Files" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.

Possible Cause:  The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain (domain\wpcsin directory) or a closed post office (post_office\wpcsin directory) because the directory is damaged.

Action:  If the input queue subdirectories are empty, you can rename the original input queue directory and then manually recreate it, along with its required subdirectories.