Hardware RAID Level & Performance

Lee lee at disinfo.com
Wed Feb 16 13:29:27 EST 2005


> 1. Use 2.6.10+ ext3, with all hashing enabled
> 2. Use an external journal in a fast device (not the RAID5 array)
>
>> Cyrus 2.3 CVS code enables you to split indexes and cyrus db files 
>> into
>> their own partition. That's where most of the i/o activity is 
>> concentrated,
>> so you only need to optimize that partition. The mail spool that 
>> remains can
>> be raid5.
>
> This is probably the best way to do it, especially if you have some
> non-volatile solid-state disks around as it was suggested  in this list
> sometime ago...
>

Do you have a particular suggestion for brand/model of device? It would 
obviously have to be redundant (or capable of being made redundant) and 
cost effectiveness would be critical.

Thanks,
L

>> Yes, ext3 does have its problems, depending on how many users and how 
>> big
>> mailboxes you have. I'd recommend reiserfs.
>
> I've heard bad things about reiserfs' capabilities to withstand
> corruption *and* to be repaired later. Something that I'd take into 
> account
> when choosing the FS for the big spools.  But maybe reiserfs has 
> non-joke
> repair utilities these days...
>
> -- 
>   "One disk to rule them all, One disk to find them. One disk to bring
>   them all and in the darkness grind them. In the Land of Redmond
>   where the shadows lie." -- The Silicon Valley Tarot
>   Henrique Holschuh
> ---
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html




More information about the Info-cyrus mailing list