Issue Details (XML | Word | Printable)

Key: JAMES-146
Type: Bug Bug
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Gabriel Kwok
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JAMES Server

File System Full

Created: 24/Dec/03 05:09 AM   Updated: 08/Sep/06 09:09 AM
Return to search
Component/s: MailStore & MailRepository
Affects Version/s: 2.1, 2.1.3, 2.2.0
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
Operating System: Other
Platform: Other

Bugzilla Id: 25736
Resolution Date: 08/Sep/06 09:09 AM


 Description  « Hide
James has a problem starting when the var/mail/<subdir> is full ... such as
the "errors" subdirectory. I noticed this because my servers gets a tonne of
spam and eventually hits the maximum number of files allowed in a directory on
Linux/Unix. I had to clean up the /var/mail/errors directory to get James
started again.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Serge Knystautas made changes - 05/Feb/04 03:15 AM
Field Original Value New Value
issue.field.bugzillaimportkey 25736 13478
Noel J. Bergman made changes - 13/Apr/04 08:34 PM
Priority Major [ 3 ]
Description James has a problem starting when the var/mail/<subdir> is full ... such as
the "errors" subdirectory. I noticed this because my servers gets a tonne of
spam and eventually hits the maximum number of files allowed in a directory on
Linux/Unix. I had to clean up the /var/mail/errors directory to get James
started again.
James has a problem starting when the var/mail/<subdir> is full ... such as
the "errors" subdirectory. I noticed this because my servers gets a tonne of
spam and eventually hits the maximum number of files allowed in a directory on
Linux/Unix. I had to clean up the /var/mail/errors directory to get James
started again.
Assignee James Developers Mailing List [ server-dev@james.apache.org ]
Environment Operating System: Other
Platform: Other
Operating System: Other
Platform: Other
Noel J. Bergman added a comment - 25/May/04 03:45 PM
Depending upon the OS and file system, there can be limits. Also the file-based repository ("file_pair" implementation) maintains an in-memory index, which expands as entries are written. There is no realy need to keep this for write-only repositories, such as error and spam.

A workaround would be to use mbox or db repositories. In the future, maildir might be an option. It is unlikely that the "file_pair" implementation will be "fixed" in terms of the total number of files, but perhaps we could add an option so that certain stores can be configured to not maintain the index, since they'll never be read.

Noel J. Bergman made changes - 25/May/04 03:45 PM
Affects Version/s 2.2.0RC2 [ 10700 ]
Affects Version/s 2.2.0RC5 [ 10721 ]
Affects Version/s 2.2.0RC4 [ 10720 ]
Affects Version/s 2.1.3 [ 10599 ]
Affects Version/s 2.2.0RC1 [ 10689 ]
Affects Version/s 2.2.0RC3 [ 10704 ]
Norman Maurer made changes - 08/Sep/06 09:09 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Won't Fix [ 2 ]