mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: andrewm@connect.com.au (Andrew McNamara)
Cc: tytso@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: Ext2, fsync() and MTA's?
Date: Sat, 12 May 2001 15:13:55 +0100 (BST)	[thread overview]
Message-ID: <E14ya9b-0004Bc-00@the-village.bc.nu> (raw)
In-Reply-To: <20010512115034.A6245285B9@wawura.off.connect.com.au> from "Andrew McNamara" at May 12, 2001 09:50:34 PM

> Under Linux, the Postfix MTA sets "chattr +S" on it's spool directories
> - obviously this hurts it's performance badly (compared to the BSD's).

Not really. BSD directory updates are always synchronous in the cases postfix
cares about. At least on the old BSD FFS/UFS file systems. Thats the only
reason the postfix stuff doesnt need it on BSD.

> It would be really nice to be able to say it's no longer necessary. It
> wants to know that a file (file data, inode and directory entry) are
> commited to stable storage when an fsync returns.

fsync guarantees the inode data is up to date, fdatasync just the data. The
directory name SuS and posix dont cover or provide any method for guaranteeing.
The convention Linux adopted is that its valid to fsync() a directory file
handle. It seemed the logical abstraction.

Alan




  reply	other threads:[~2001-05-12 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-12 11:50 Andrew McNamara
2001-05-12 14:13 ` Alan Cox [this message]
2001-05-12 14:53   ` Andrew McNamara
2001-05-12 15:20     ` Theodore Tso
2001-05-21 17:47     ` Stephen C. Tweedie
2001-05-21 22:04       ` Theodore Tso
2001-05-22 15:50         ` Oliver Xymoron
2001-05-22 16:48           ` Stephen C. Tweedie
2001-05-22 16:54             ` Oliver Xymoron
2001-05-22 16:57               ` Stephen C. Tweedie
2001-05-24  1:48       ` Marco d'Itri
2001-05-21 17:41   ` Stephen C. Tweedie

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=E14ya9b-0004Bc-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=andrewm@connect.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@valinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®