4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: journaling fi...
FromSent OnAttachments
Anand BuddhdevMay 13, 2002 1:45 pm 
Sam VarshavchikMay 13, 2002 2:55 pm 
Juri HaberlandMay 14, 2002 12:38 am 
Ralf HildebrandtMay 14, 2002 2:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: journaling filesystems and fsyncActions...
From:Juri Haberland (habe@altus.de)
Date:May 14, 2002 12:38:41 am
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Anand Buddhdev writes:

Sam,

If the courier-mta queue is mounted on a journaling filesystem like ext3 or reiserfs, is it safe to use the --without-explicitsync option?

I don't know. I haven't looked at them in great detail. Although they'll certainly recover to a consistent state, after a crash, the issue's whether they'll get there simply by tossing out enough stuff as to get back to a known consistent state, but not necessarily one with the most recent data.

For ext3, at least, you have several logging options, such as metadata only, or metadata and data. Metadata only is obviously not enough, so you'll need to log both data and metadata.

Hmm, it is said that at least Postfix is save on ext3 without setting the spool dir to do syncronous i/o. Postfix normally does a 'chattr +S' on install. Search the postfix-users ML for ext3 to see the discussion and also replies from Stephen Tweedie.

Cheers, Juri

-- If each of us have one object, and we exchange them, then each of us still has one object. If each of us have one idea, and we exchange them, then each of us now has two ideas.