All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Bennett Todd <bet@rahul.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Status of fsync() wrt mail servers
Date: 10 Sep 2003 07:14:34 -0400	[thread overview]
Message-ID: <1063192474.18154.355.camel@tiny.suse.com> (raw)
In-Reply-To: <20030910105102.GA535@rahul.net>

On Wed, 2003-09-10 at 06:51, Bennett Todd wrote:
> 2003-09-10T01:29:53 lists@unbeatenpath.net:
> > I'm in the process of researching OSes and filesystems for a new mail
> > system.  I'm hoping to use linux+reiserfs+postfix, and I'm wondering
> > where reiserfs stands wrt to fsync().  Does reiserfs provide a mechanism
> > to have truly synchronous writes with a single fsync() call?  Thanks
> 
> I'm not really fond of the phrase "truly synchronous writes"; it can
> be read different ways by different people.
> 
> What postfix demands (if you wish to adhere strictly to some
> peoples' interpretations of RFCs) is that when fsync returns, the
> filesystem guarantees that even if there's a crash an instant after,
> the file, data as well as metadata, will be intact when the machine
> comes up again. This is in support of a desire to positively commit
> to the sender that the receiving MTA has accepted receipt for a
> message.

This is what reiserfs does, the metadata is on disk after an fsync,
including any renames.

-chris


  reply	other threads:[~2003-09-10 11:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  5:29 Status of fsync() wrt mail servers lists
2003-09-10 10:51 ` Bennett Todd
2003-09-10 11:14   ` Chris Mason [this message]
2003-09-10 11:41     ` Bennett Todd
2003-09-10 12:30       ` Chris Mason
2003-09-10 15:18         ` Cameron Moore
2003-09-10 21:32           ` Mike Fedyk
2003-09-10 22:33             ` Cameron Moore
2003-09-10 23:49               ` Mike Fedyk
2003-09-11 12:33                 ` Matthias Andree
2003-09-11 17:25                   ` Mike Fedyk
2003-09-12  0:22                     ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1063192474.18154.355.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=bet@rahul.net \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.