( Sorry,again but I did not get an answer until now)
Hello Bron
2008/2/25, Bron Gondwana <[EMAIL PROTECTED]>:
> On Mon, Feb 25, 2008 at 05:52:34PM +0100, Martin Schweizer wrote:
> > >
> > > > I use FreeBSD 6.3 and cyrus 2.3.11. Below is the manual for the
> change.
> > > >
> >
>it takes long enough to rebuild an array with large drives that the
>chances of a second drive failing during the rebuild become noticable.
Worse, the act of rebuilding can prompt a second, marginal disk to fail.
Presumably the mechanics are the head runs through a patch of debris in
an otherwise
Does anybody know if this will work with cyrus to create some kind of
cyrus cluster? or at least a failover?
http://www.drbd.org/
Thanks
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing
Hi,
I made some tests with sieve vacation and it works great !
But the record (timestamp) wrote on deliver.db from expiration time seems
only accept the minimum of 3 days !
Is this a feature ??
I'm using cyrus-imapd version 2.2.13 on a debian etch.
Thanks.
Cyrus Home Page: http://cyrusima
On Tue, 4 Mar 2008, Ian G Batten wrote:
> software RAID5 is a performance
> disaster area at the best of times unless it can take advantage of
> intimate knowledge of the intent log in the filesystem (RAID-Z does
> this),
actually, unless you have top-notch hardware raid controllers, software ra
On 28 Feb 08, at 2256, Kenneth Marshall wrote:
> It may be that the software RAID 5 is your problem. Without the
> use of NVRAM for a cache, all of the writes need all 3 disks.
> That will cause quite a bottle-neck.
In general, RAID5 writes require two reads and two writes,
independent of the
