From: "Stephen C. Tweedie" <sct@redhat.com>
To: Beau Kuiper <kuib-kl@ljbc.wa.edu.au>,
linux-kernel@vger.kernel.org, tovarlds@transmeta.com,
Stephen Tweedie <sct@redhat.com>
Subject: Re: [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes
Date: Mon, 24 Sep 2001 15:37:00 +0100 [thread overview]
Message-ID: <20010924153700.B13817@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0109201445170.13543-100000@gamma.student.ljbc> <20010921152627.C13862@emma1.emma.line.org>
In-Reply-To: <20010921152627.C13862@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Fri, Sep 21, 2001 at 03:26:27PM +0200
Hi,
On Fri, Sep 21, 2001 at 03:26:27PM +0200, Matthias Andree wrote:
> Be careful! MTAs rely on this behaviour on fsync(). The official
> consensus on ReiserFS and ext3 on current Linux 2.4.x kernels (x >= 9)
> is that "any synchronous operation flushes all pending operations", and
> if that is changed, you MUST make sure that the changed ReiserFS/ext3fs
> still make all the guarantees that softupdated BSD file systems make,
> lest you want people to run their mail queues off "sync" disks.
Reiserfs and ext3 have their own IO ordering --- they don't commit
transactions until the log writes for _all_ of the blocks in those
transactions have been acknowledged. Reordering outstanding IOs won't
affect the fsync guarantees at all.
--Stephen
next prev parent reply other threads:[~2001-09-24 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 7:12 [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes Beau Kuiper
2001-09-20 12:16 ` Chris Mason
2001-09-20 15:20 ` Beau Kuiper
2001-09-20 16:15 ` Andreas Dilger
2001-09-20 16:22 ` Beau Kuiper
2001-09-21 20:12 ` Lehmann
2001-09-21 20:57 ` Rik van Riel
2001-09-21 22:50 ` Lehmann
2001-09-21 13:26 ` Matthias Andree
2001-09-22 18:38 ` Beau Kuiper
2001-09-22 19:32 ` Matthias Andree
2001-09-23 15:24 ` Chris Mason
2001-09-24 14:37 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 17:23 Chris Mason
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=20010924153700.B13817@redhat.com \
--to=sct@redhat.com \
--cc=kuib-kl@ljbc.wa.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tovarlds@transmeta.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.