On 2015-04-23 00:18, James Macdonell wrote:
I could see tweaking a directory scheme to include the year and month.
So, the directories would by 4- or 5-levels:
./2015/04/ff/fff/ff/
That would make it easier to use the symlink suggestion from
extremeshok.
Actually the top level store dirs, eg. 551, 552, 553, ... refer to the
date. Each such directory holds ~12 days of emails. So if you are
writing
to 553, then you can be sure that no previous dirs (..., 551, 552)
changes
any more. (Except if you remove old emails with pilerpurge).
Anyway some other ideas emerged on the bitbucket page.
Related to the topic, it would be useful to have the storage scheme
mentioned in the install documents. I might have tweaked my inode
ratio had I known each message was stored as a file.
I've just added your note to the installation manual.
What I ended up doing was making /var a logical volume sitting on vg
containing of two AWS "physical" volumes. That way I could add more
physical volumes and extend the LV as needed. Not quite what the
request is for, but it's similar.
On 04/22/2015 06:44 AM, Janos SUTO wrote:
Dear piler-users,
I'm not sure if you like the way piler stores message files, eg.
zillions of small files in a 3-level dir structure.
Someone asked for supporting multiple storages
(https://bitbucket.org/jsuto/piler/issue/540/multiple-storage).
I'd like to hear your opinions on the matter as well.
Janos
