Bron Gondwana wrote:
> On Tue, Sep 04, 2007 at 02:28:35PM -0400, Wesley Craig wrote:
>> Just to be clear, that's cyr_expire dying, not being killed by
>> master. Signal 11 is SIGSEGV, which is to say a segmentation
>> violation, i.e., a bug in cyr_expire. Personally, I've seen this
>> error
On Tue, Sep 04, 2007 at 02:28:35PM -0400, Wesley Craig wrote:
> Just to be clear, that's cyr_expire dying, not being killed by
> master. Signal 11 is SIGSEGV, which is to say a segmentation
> violation, i.e., a bug in cyr_expire. Personally, I've seen this
> error on a lot of systems. The
On Tue, 2007-09-04 at 10:19 +0100, David Carter wrote:
> I also gather that the xfs repair tools need an extraordinary amount of
> memory to run on large file systems:
>
>http://oss.sgi.com/archives/xfs/2005-08/msg00045.html
I had this problem recently. Newer versions of xfsprogs fix it:
ht
On Sep 4, 2007, at 15:42:05, Corey Bobb wrote:
> Hello,
>
>
>
> I have inherited a mail system that runs cyrus21, since I have
> never ran this setup before I am not quite sure how to troubleshoot
> some problems. The current problem I am having is that I am
> receiving mail from my outsid
I'm finally getting around to upgrading my 2.3.7 system to 2.3.9. When I
put in 2.3.7 I had to patch a few things to make it work properly on
64-bit SPARC, mainly unaligned dereferences causing BUS faults due to
the SPARC MMU.
Thankfully 2.3.9 has most of these sorted, mainly through using align_
Hello,
I have inherited a mail system that runs cyrus21, since I have never ran
this setup before I am not quite sure how to troubleshoot some problems.
The current problem I am having is that I am receiving mail from my outside
email relay (postfix) which From what I gather forwards it over th
Just to be clear, that's cyr_expire dying, not being killed by
master. Signal 11 is SIGSEGV, which is to say a segmentation
violation, i.e., a bug in cyr_expire. Personally, I've seen this
error on a lot of systems. The mailbox after the last one you listed
probably has a corrupt meta fi
>> May somebody recommend reliable/safe filesystem that support resizing?
>> I'm afraid to use anything except ext3 in production enviroment...
>>
Forgot to mention for ZFS, you can grow the pool by adding disks to it.
We run a pool full of mirror pairs so we'd add more pairs.
Quite easy an
>
>> May somebody recommend reliable/safe filesystem that support resizing?
>> I'm afraid to use anything except ext3 in production enviroment...
>>
We use Solaris and I have to say ZFS is quite amazing. Never have to
run fsck ever again!
The checksum feature ensures that when you read the
deliver.db keep only the last message id received, and the recipients,
not the mailbox/folder where they are stored/moved.
The db is purged regularly, a least when running cyr_expire from
oldest messages-id.
I thing you have to check every mailbox one by one ...
On 9/4/07, [EMAIL PROTECTED] <[EMA
On Tue, 4 Sep 2007 10:09:40 +0100 (BST), "David Carter" <[EMAIL PROTECTED]>
said:
> On Tue, 4 Sep 2007, Bron Gondwana wrote:
>
> > Ah - yeah, that's right. Except that the restart only got negotiated
> > after each folder was processed, and if you're pushing a new folder with
> > 200,000 mess
Hello,
I'm busy writing a perl script that will parse our cyrus logs for the
most important errors.
While going trough them I found the following, on the server that runs
one of our replica's:
mail3r/master[27338]: about to exec /usr/cyrus-replica/bin/cyr_expire
mail3r/cyr_expire[27338]: Expun
David Carter a écrit :
> On Tue, 4 Sep 2007, Bron Gondwana wrote:
>
>> Ah - yeah, that's right. Except that the restart only got negotiated
>> after each folder was processed, and if you're pushing a new folder
>> with 200,000 messages (say, after a user move in our case) then that
>> got a bi
> We are using XFS on LVM for years now with cyrus-imapd and it has always
> worked very well. Online expansion with this combination has saved us from
> many hours of downtime over the years.
>
> Simon
>
Checking several 1Tb-20Tb filesystem with large amount of small files
will take a while..
I am looking for a way to locate a message in any folder.
Of course I could examine all folders in turn for a given message id,
but the way cyrus does duplicate elimination across folders suggests that
there might be a more efficient way.
Intended purpose: record message-id of certain mails outside
On Tue, 4 Sep 2007, Bron Gondwana wrote:
; Does this mean there is no way to get single-instance-store on a replica
; if you're rebuilding it from scratch?
I've always used rsync to initialise the replica since that will
preserve the hard links - so rsync followed by shutdown, rsync
again and remo
On Tue, 4 Sep 2007, Artem Bokhan wrote:
> Checking several 1Tb-20Tb filesystem with large amount of small files
> will take a while... based on my experience xfs sometimes need full
> check after power failure, for example.
I also gather that the xfs repair tools need an extraordinary amount of
On Tue, 4 Sep 2007, Bron Gondwana wrote:
> Ah - yeah, that's right. Except that the restart only got negotiated
> after each folder was processed, and if you're pushing a new folder with
> 200,000 messages (say, after a user move in our case) then that got a
> bit memory hungry and all sorts i
On Tue, 4 Sep 2007 09:15:32 +0100 (BST), "David Carter" <[EMAIL PROTECTED]>
said:
> On Tue, 4 Sep 2007, Bron Gondwana wrote:
>
> > for all the users across which the single instance store needs to
> > apply, then run 'sync_client -r -f $file'.
>
> I typically use "-u -f" to do this. However:
>
>
>> Cyrus puts one folder on one partition. you can put subfolders on
>> other partitions, but you cant have two partitions connected with one
>> folder.
>> Cyrus has no way to decide where it would store the email on disk and
>> it would cost more time to merge these partitions in memory if a use
> Hello,
>
> We had a properly working postfix + cyrus-imap system till 23rd of
> July. Then messages like the below one started to appear in the log
> file.
>
> Sep 3 07:45:59 srv1 deliver[20650]:
> connect(/var/lib/imap/socket/lmtp) failed: Connection refused
>
> The postfix log shows:
>
> Sep
On Tue, 4 Sep 2007, Bron Gondwana wrote:
> for all the users across which the single instance store needs to
> apply, then run 'sync_client -r -f $file'.
I typically use "-u -f" to do this. However:
> Creating files like this and passing them with the -f flag forces
> sync_client to consider th
Bron Gondwana ?:
> Besides,
> how are you planning to decide which messages go on which partition?
> Some sort of hash of the UID?
>
>
Possible, just configurable ratio balancing...
> (reiserfs, it's the only Linux filesystem
> with anywhere _near_ the performance profile under heavy load
Bron Gondwana ?:
> Besides,
> how are you planning to decide which messages go on which partition?
> Some sort of hash of the UID?
>
>
Possible, just configurable ratio balancing...
> (reiserfs, it's the only Linux filesystem
> with anywhere _near_ the performance profile under heavy load
24 matches
Mail list logo
