Hello,
I am also quite interested in this topic as I will be using Solaris 9 with
UFS logging enabled on each slices. Can others from this mailing list
confirm that disabling UFS logging on the Cyrus slice (partition) will
speed up the "ctl_cyrusdb -r" process ? I guess if it's recommended to turn
off UFS logging, it would be good to have this somewhere in the Cyrus
documentation or maybe in the FAQ...
Regards
Marc
John Havard To:
[EMAIL PROTECTED]
<[EMAIL PROTECTED]> cc: Jatin Nansi
<[EMAIL PROTECTED]>
Sent by: Subject: Re: ctl_cyrusdb -r
takes too long
[EMAIL PROTECTED]
ew.cmu.edu
12/16/02 06:17 PM
You wouldn't happen to have have /var/imap on a logging or journaling
filesystem by any chance? A while back I noticed this under Solaris. The
fix was to mount /var without UFS logging. IIRC, the db code does its own
journaling/logging, so the only thing you'll be missing by turning it off
in the FS is the long start times.
Regards,
John Havard
Systems Administrator
Internet Doorway, Inc.
Internet Doorway, Inc. (NETDOOR) - "Mississippi's ISP"
601.969.1434 | 800.952.1570 | http://www.netdoor.com/
--On Saturday, December 14, 2002 05:50:33 PM +0530 Jatin Nansi
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> This is for cyrus gurus and for record:
>
> -------------------------------------------------------
> Dec 13 20:10:21 mail3 master[4574]: process started
> Dec 13 20:10:21 mail3 master[4575]: about to exec
> /usr/cyrus/bin/ctl_cyrusdb Dec 13 20:10:21 mail3 ctl_cyrusdb[4575]:
> recovering cyrus databases Dec 14 06:15:11 mail3 ctl_cyrusdb[4575]: done
> recovering cyrus databases Dec 14 06:15:11 mail3 master[4574]: ready for
> work
> Dec 14 06:15:11 mail3 master[4979]: about to exec
> /usr/cyrus/bin/ctl_cyrusdb Dec 14 06:15:11 mail3 master[4982]: about to
> exec /usr/cyrus/bin/imapd Dec 14 06:15:11 mail3 master[4983]: about to
> exec /usr/cyrus/bin/imapd Dec 14 06:15:11 mail3 master[4984]: about to
> exec /usr/cyrus/bin/lmtpd Dec 14 06:15:11 mail3 master[4985]: about to
> exec /usr/cyrus/bin/lmtpd Dec 14 06:15:11 mail3 master[4981]: about to
> exec /usr/cyrus/bin/tls_prune Dec 14 06:15:11 mail3 master[4980]: about
> to exec /usr/cyrus/bin/ctl_deliver Dec 14 06:15:11 mail3
> ctl_cyrusdb[4979]: checkpointing cyrus databases Dec 14 06:15:11 mail3
> lmtpunix[4985]: executed
> Dec 14 06:15:11 mail3 lmtp[4984]: executed
> Dec 14 06:15:11 mail3 tls_prune[4981]: mydelete: starting txn 2147483653
> -------------------------------------------------------
>
> Will ctl_cyrusdb -r take 10 hours ? I dread the day when the system will
> need downtime again.
>
> This is on a decent 2 x P3 1 GHz with 100 GB scsi raid and 1 GB RAM,
> about 2000 users, 50 MB per user.
>
> I really need reboot times to be between 5 to 10 minutes, as against 10
> hours. I will set the checkpoint period to 5 minutes as per the FAQ, but
> are there any other pointers ?
>
> Jatin
>
>
>
>
> Jatin Nansi wrote:
>
>> Hi,
>>
>> I have a cyrus IMAP system here which is taking way too long to start
>> up, stopping just at ctl_cyrusdb -r. There does not seem to be any
>> activity going on, but ctl_cyrusdb just doesnot exit.
>>
>> I am running cyrus-imapd-2.1.8 on a redhat 7.3 system. The backend
>> database is DB3.
>>
>> I need some directions on what could be wrong and where ? Is it normal
>> for ctl_cyrusdb -r to take as much as 1 hr (and still running) to
>> finish ?
>>
>> Jatin
>>
>
>
