News for hackers. Stuff that matters.
Re:"mbox" is a family of several mutually incompatible mailb... by JoshTriplett on Sunday January 08, 2012 @06:35AM (#3439356)
On a relatively small ext4 filesystem here, I have tens of millions of inodes available, and I haven't done anything to tweak that. On a larger filesystem, with a slightly bumped number of inodes, I'd expect several hundred million inodes, more than enough to store all the messages that'll fit in the available space.

As for listing and manipulating, I'd suggest not ever listing all the files. Access them by name only, which should require near-constant time no matter how many files you have. Manipulating the files should take similarly little time. On the occasions that you do need to list all the files, you might find https://www.olark.com/spw/2011/08/you-can-list-a-directory-w... interesting.

A pile of RAM helps, to keep as many directory entries in the dcache as possible.

Re:"mbox" is a family of several mutually incompatible mailb... by mike-cardwell on Sunday January 08, 2012 @10:15AM (#3439662)
Email can use up inodes quickly. A thousand users with a thousand emails each is a million files in Maildir. Plus three directories (cur/new/tmp) for each mail folder.
Re:"mbox" is a family of several mutually incompatible mailb... by JoshTriplett on Sunday January 08, 2012 @02:32PM (#3440277)
Folders seem unlikely to use up a significant number of inodes compared to the messages. As for messages, how many users do you expect to serve from each mail server? I think you'll hit the limits of whatever service you want to provide before you hit the limit of inodes in your mail store.

(Or you could always encrypt each email and throw it at an object storage system similar to S3. ;) )