Re: best filesystem for imap server

2004-12-07 Thread Einar Indridason
On Sun, Dec 05, 2004 at 12:43:14AM -0200, Henrique de Moraes Holschuh wrote:
> On Sat, 04 Dec 2004, Einar Indridason wrote:
> > 
> > Don't forget JFS from IBM.
> 
> All I know about JFS is that it did not come up as better enough than ext3
> in a few benchmarks I've seen, to bother with it at the time :(
> 
> If you have first hand experience with JFS, please describe it to us.
> Especially data protection capabilities and performance in ridiculously big
> directories, as required by Cyrus spools :)

I don't have a first hand experience with JFS.  I just found it to be
missing from the discussion.

We do have some *huge* mail-folders here, running on ext3, and when a
directory gets over a certain size, every operation on the directory
increases in time very sharply.  (Due to the "linked list" implementation
in ext2/ext3.)

We did some googling around regarding which filesystem to choose, and I'm
inclined to try JFS when we install the next mail-server.

Some URLs I stumbled upon:

http://linuxgazette.net/102/piszcz.html
http://jamesthornton.com/hotlist/linux-filesystems/

And of course:
http://www.google.com/search?q=journaled+filesystem+benchmark+linux


--
einari
---
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


Re: best filesystem for imap server

2004-12-04 Thread Einar Indridason
On Wed, Dec 01, 2004 at 05:07:46PM -0600, Jim Miller wrote:
> 
> 
> I feel that XFS is a bad choice since it is not a 'truly' journaled file
> system.  If you have a power failure/system crash/lockup, etc., etc. You
> could very easily end up with a corrupt file system -- XFS doesn't write out
> to the disks immediately (caching unwritten data to memory).  EXT3 is
> journaled but very slow.  ReiserFS is a better choice for a journaled file
> system and if you can hold off until all the bugs are worked out, Reiser4FS
> would be the best choice (IMHO).


Don't forget JFS from IBM.

--
[EMAIL PROTECTED]
---
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


Re: Weird mailbox corruption...

2003-10-30 Thread Einar Indridason
On Thu, Oct 30, 2003 at 10:13:30AM +0800, Craig Ringer wrote:
> >Until we get something like:
> >
> >user.JohnSmith.Folder.Sub folder
> >user.JohnSmith.Folder.Sub folder.Comet: Mailbox has an invalid format 
> >user.JohnSmith.Folder.Sub folder.Comet.AI False: System I/O error No such 
> >file or directory
> >user.JohnSmith.Folder.Sub folder.Comet.Ceco Work: Mailbox has an invalid 
> >format user.JohnSmith.Folder.Sub folder.Comet.Ceco Work.AI False: Mailbox 
> >has an invalid format user.JohnSmith.Folder.Sub folder.Comet.Ceco 
> >Work.Ceco Work: System I/O error No such file or directory
> >user.JohnSmith.Folder.Sub folder.Comet.Ceco Work.Magistr: Mailbox has an 
> >invalid format 

Right... I managed to fix this, but it was not quite in a
straightforward way.

In a very short summary:

Make sure the files on the filesystem, and cyrus's view are the same.
Use cyradm, to make sure that every Mailbox has a valid list of
permissions.

One might have to create mailboxes or delete them, via cyradm, to make
those two consistent.

One might have to copy (or even touch) the 3 cyrus.* files to the proper
directory, making sure the permissions on the files are correct, and
then run reconstruct on that folder.

So... a careful juggling between cyradm, reconstruct and filesystem-operations
fixed this.  

Cheers,
--
[EMAIL PROTECTED]


Re: Weird mailbox corruption...

2003-10-30 Thread Einar Indridason
On Thu, Oct 30, 2003 at 10:13:30AM +0800, Craig Ringer wrote:

> >
> Could the filesystem /var/spool/imap is on have filled up? Just a guess...

(Sorry, I pressed the "reply-to" button, before I was awake... I should have
pressed the "group-reply" button.)

No, the filesystem did not fill up.  However, we did experience a
"resource starvation", due to the machine using up all the free
file-descriptors we had available.  (We have since bumped up the numbers
of free file-descriptors, in order to reduce this from happening again.)

> >If I go into "cyradmin", then that user and his folders do look allright
> >to me.
> 
> That'll have to wait for the cyrus wizards. One of the things I'm 
> planning to do is start a "cyrus backup, restoration and recovery" FAQ. 
> Note the "planning to do" not "have done".

Yebb, so noted :-)

But thanks,
[EMAIL PROTECTED]



Weird mailbox corruption...

2003-10-29 Thread Einar Indridason
Hi folks.

(I'm using version 2.1.15 of the Cyrus Imap server, version 2.1.15
of SASL, and Berkeley DB version 4.1.25)

I'm experiencing a weird corruption... I have user here... some of
his folders work (have the cyrus.* files).  But one of his folder, and
the INBOX as well... they don't work.  I have tried "reconstruct" with
all the possible combination of -r, -f, and -x, but still no go.

If I do:
[EMAIL PROTECTED] cyrus]$ reconstruct -r -f user.JohnSmith

I get:

user.JohnSmith: Mailbox has an invalid format< HMM
user.JohnSmith.My Stuff.Book A Day
user.JohnSmith.My Stuff.Book A Day.Fiction

And we get several lines with valid and fine subfolders...
...

Until we get something like:

user.JohnSmith.Folder.Sub folder
user.JohnSmith.Folder.Sub folder.Comet: Mailbox has an invalid format 
user.JohnSmith.Folder.Sub folder.Comet.AI False: System I/O error No such file or 
directory
user.JohnSmith.Folder.Sub folder.Comet.Ceco Work: Mailbox has an invalid format 
user.JohnSmith.Folder.Sub folder.Comet.Ceco Work.AI False: Mailbox has an invalid 
format 
user.JohnSmith.Folder.Sub folder.Comet.Ceco Work.Ceco Work: System I/O error No such 
file or directory
user.JohnSmith.Folder.Sub folder.Comet.Ceco Work.Magistr: Mailbox has an invalid 
format 

This goes on for this "Sub folder".  (He has other folders, with space
in the name, and those folders are ok.)

If I go into "cyradmin", then that user and his folders do look allright
to me.


So... Any hints would be apreciated.

Thanks in advance,
-- 
[EMAIL PROTECTED]


Re: Subject field corruption

2003-06-06 Thread Einar Indridason
On Thu, Jun 05, 2003 at 08:57:38PM +0400, NOwlar wrote:
> I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
> The problem is as follow:
> When a message with russian charset characters (KOI8-R, WIN1251) in Subject
> field arrives or is moved into the Sent Items folders by Outlook Express,
> each russian character is replaced by an X (ex: Re:   mazda 626
> ). I happens only when the Subject field is without charaterset
> specification.
> 
> I dumped mailboxes with cyrdump, the Xes are in.
> 
> What can be wrog?
> 
> I will appreciate any help.
> Max.

Cyrus kills the 8th bit character in the header, and replaces it with 'X'.  
There is a configuration option, that would discard unconditionally every 
message with the 8th bit turned on in the headers.  Luckily you are *only* 
seeing the 'X' inserted instead.

In Cyrus-2.0.16 one file needed to be patched.  In the latest Cyrus-es
you apparently need to patch 2 files.

In my opinion, this breaks the "Be liberal in what you accept, strict in
what you send".

Unfortunately (regardless of what the developers of Cyrus think) there
are still software out there that generates email messages with 8th bit
headers.

--
[EMAIL PROTECTED]