> -----Original Message----- > From: Angus Lee > Sent: Tuesday, February 22, 2005 9:01 PM
[ Snip ] > I cannot reproduce the error myself. because i cannot read > these dead file. > So, maybe special character within the mail file cause the > error? i dunno. If so, it's not the mail software's fault. Your server is broken. > And i can't find a way to figure it out. My server mainly > user is Chinese, with charset zh-TW and zh-CN. There're lots > of email with chinese title and content. And i guess > courier-imap should handle locale quite well. Look, any Unix (including Linux) file can contain any value. There are no special characters. Even in file *names*, no character will cause a system problem (although it may produce errors for the application trying to create the file). [ Snip ] > My existing kernel is 2.6.5-1.358. I know that i should > update to the newest kernel. However, i cannot reboot the > server for kernel upgrade now because these dead email file > will certainly make the bootup filesystem check fail and the > worse case is corrupt that partition. I guess that somebody > else should use this default FC2 kernel as well with no > filesystem related problem. I searched the ChangeLog in FC2 > between this old kernel and most updated kernel and no such > filesystem related bug fixes. (maybe i was wrong) Look, your server is broken. Courier does nothing below the application level, so if you have problems that filesystem checking finds, the problem lies either with your hardware or your kernel. > I'm not trying to say that i rejected the possibility for the > source of problem from this kernel. I'd like to know if > someone tell me that "yes, this kernel version is buggy and > will produce corrupted file at ext3 filesystem in some > manner", so i can simply format this server, update kernel, > re-install anything and done. But seems that the problem is > not that exact. I know that i should try to upgrade kernel > version, but are there any possible solution besides this? I > think that this is my last last step if i really can't find solution. I will be authoritative: Courier CANNOT break a properly functioning system in the way you describe. So therefore your system itself is broken. This is not up for debate. Courier *only* uses legal filesystem operations, so if boot-time checks find errors on the filesystem, Courier did NOT create them. > For these dead email file, i cannot find any I/O related > error in syslog. > And I'm quite certain that this is not a hardware failure. > > Again, thx for anyone reading this and i hope that i can > solve this problem asap. YOU NEED TO FIX YOUR SYSTEM. FORGET COURIER. FORGET E-MAIL. YOUR SYSTEM IS BROKEN. WHEN YOUR SYSTEM IS NO LONGER BROKEN, COURIER WILL RUN FINE. Malc. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
