From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: linux-kernel@vger.kernel.org
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Subject: Re: [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts
Date: Mon, 15 Jul 2002 12:14:24 -0400 [thread overview]
Message-ID: <20020715121424.B2316@ti20> (raw)
In-Reply-To: <20020715153553.GC22828@merlin.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Mon, Jul 15, 2002 at 05:35:53PM +0200
On Mon, Jul 15, 2002 at 05:35:53PM +0200, Matthias Andree wrote:
> The code is there, for ext3, but not for reiserfs. A year has passed,
> but still, dirsync is not the default. This is directed towards the
> maintainers of the kernel, not towards Andrew Morton.
I'm in violent agreement that it should go into 2.4 *now that it is merged
in 2.5*. You may have noticed that Marcelo has been occupied with a few
other issues (VM, IDE).
> > I don't have dirsync handy at the moment, so I can't test, but
> > I have to ask: have you tried the simple (and IMHO devastating) benchmark
> > that I posted back on 2001-08-02 comparing Linux to Solaris file creation,
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=99678208121947&w=2
> >
> > i.e., copy a file tree (XFree86-4.1, 33027 files) with hard links.
>
> Nope, I prefer not to play disk hogging games on my Solaris boxen, both
> of which are in production :-)
I'm not asking you to do it on your Solaris boxen -- I couldn't give a
damn about slow, buggy Solaris I'm asking whether you have tested this
on ext2/ext3 with/without dirsync. The gentlemanly thing to do when asking
for a change to the kernel is to (honestly) assess its impact.
> So you prefer speed over safety. That's fine. But that's not sane for a
> kernel to do. Cheating benchmarks is what others may call it. I just
> call it sad.
Cheating benchmarks -- bah! Safety for *one* (naive) application class!
dirsync buys me no useful safety on my build host, all it will do is
slow down things like rpmbuild --rebuild.
This is all rather silly. An MTA requires configuration, so what is
the difficulty in using -o dirsync, or alternatively, and quite a bit
more simply, executing chattr +D on the spool directory. It's quite
simple: put dirsync in the kernel and tools, then add chattr +D to the
post-install scripts for your favorite package manager.
- Bill Rugolsky
next prev parent reply other threads:[~2002-07-15 16:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 13:49 [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories on NFS mounts Trond Myklebust
2002-07-09 14:06 ` Richard B. Johnson
2002-07-09 14:08 ` Trond Myklebust
2002-07-09 15:06 ` Richard B. Johnson
2002-07-09 15:06 ` Richard B. Johnson
2002-07-09 16:56 ` Alan Cox
2002-07-09 16:56 ` Alan Cox
2002-07-09 17:22 ` Richard B. Johnson
2002-07-09 17:22 ` Richard B. Johnson
2002-07-09 18:58 ` [NFS] " Bill Rugolsky Jr.
2002-07-09 18:58 ` Bill Rugolsky Jr.
2002-07-09 19:11 ` Alan Cox
2002-07-09 19:11 ` Alan Cox
2002-07-09 19:13 ` Richard B. Johnson
2002-07-09 19:13 ` Richard B. Johnson
2002-07-09 19:39 ` [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine fordirectories " David Dillow
2002-07-09 19:59 ` [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories " Alan Cox
2002-07-09 19:59 ` Alan Cox
2002-07-09 19:50 ` Richard B. Johnson
2002-07-15 7:52 ` Sean Hunter
2002-07-15 12:45 ` Richard B. Johnson
2002-07-15 12:45 ` Richard B. Johnson
2002-07-15 13:35 ` Matthias Andree
[not found] ` <mit.lcs.mail.linux-kernel/20020715133507.GF32155@merlin.emma.line.org>
2002-07-15 14:49 ` Patrick J. LoPresti
2002-07-15 15:18 ` Matthias Andree
[not found] ` <mit.lcs.mail.linux-kernel/20020715151833.GA22828@merlin.emma.line.org>
2002-07-15 16:10 ` Patrick J. LoPresti
2002-07-15 18:16 ` Matthias Andree
[not found] ` <mit.lcs.mail.linux-kernel/20020715181650.GA20665@merlin.emma.line.org>
2002-07-15 18:56 ` Patrick J. LoPresti
2002-07-15 20:50 ` Matthias Andree
2002-07-15 16:16 ` Alan Cox
2002-07-15 15:19 ` Matthias Andree
2002-07-15 16:45 ` Alan Cox
2002-07-15 15:38 ` Patrick J. LoPresti
2002-07-15 16:55 ` Alan Cox
2002-07-15 15:29 ` [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine fordirectories " Sandy Harris
2002-07-15 20:17 ` [PATCH] 2.4.19-rc1/2.5.25 provide dummy fsync() routine for directories " Patrick J. LoPresti
2002-07-16 1:40 ` jw schultz
2002-07-15 15:20 ` Bill Rugolsky Jr.
2002-07-15 15:35 ` Matthias Andree
2002-07-15 16:14 ` Bill Rugolsky Jr. [this message]
2002-07-09 19:50 ` Richard B. Johnson
2002-07-09 14:08 ` Trond Myklebust
2002-07-10 6:33 ` Alex Riesen
2002-07-10 11:20 ` Richard B. Johnson
2002-07-09 14:06 ` Richard B. Johnson
2002-07-11 10:52 ` Matthias Andree
2002-07-11 11:26 ` Trond Myklebust
[not found] <E17SjDh-00067R-00@usw-sf-list2.sourceforge.net>
2002-07-11 19:14 ` Rex Dieter
2002-07-11 20:05 ` Tom McNeal
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 13:49 Trond Myklebust
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=20020715121424.B2316@ti20 \
--to=brugolsky@telemetry-investments.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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.