From: Bennett Todd <bet@rahul.net>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Status of fsync() wrt mail servers
Date: Wed, 10 Sep 2003 07:41:03 -0400 [thread overview]
Message-ID: <20030910114103.GA26767@rahul.net> (raw)
In-Reply-To: <1063192474.18154.355.camel@tiny.suse.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
2003-09-10T07:14:34 Chris Mason:
> On Wed, 2003-09-10 at 06:51, Bennett Todd wrote:
> > 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.
Metadata, yes, I've got that. How about the data? Does return from
fsync guarantee that the data will be intact as well?
-Bennett
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-10 11:41 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
2003-09-10 11:41 ` Bennett Todd [this message]
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=20030910114103.GA26767@rahul.net \
--to=bet@rahul.net \
--cc=mason@suse.com \
--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.