From: Hans Reiser <reiser@namesys.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Oleg Drokin <green@namesys.com>,
Nikita Danilov <Nikita@Namesys.COM>,
Xuan Baldauf <xuan--reiserfs@baldauf.org>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
zam@thebsh.namesys.com
Subject: Re: Feature request: online fsync disable
Date: Thu, 05 Sep 2002 14:39:19 +0400 [thread overview]
Message-ID: <3D773457.6050601@namesys.com> (raw)
In-Reply-To: 20020905035604.GB6004@tapu.f00f.org
Chris Wedgwood wrote:
>On Fri, Aug 23, 2002 at 03:59:58PM +0400, Hans Reiser wrote:
>
> It is a reasonable feature request I think.
>
>No it's not.
>
>It's a terrible idea. If someone calls fsync, they call it for a
>reason and have various expectations.
>
Usually these expectations involve a user not wanting to use mkreiserfs
at every boot. If the expectations are wrong, then all power to the user.
> You should not throw these
>away or else you may as well just start writing random data all over
>the place.
>
>
>
> --cw
>
>
>
>
next prev parent reply other threads:[~2002-09-05 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 11:29 Feature request: online fsync disable Xuan Baldauf
2002-08-23 11:52 ` Nikita Danilov
2002-08-23 11:56 ` Oleg Drokin
2002-08-23 11:59 ` Hans Reiser
2002-08-23 12:09 ` Nikita Danilov
2002-08-23 13:08 ` Chris Mason
2002-08-23 18:10 ` Xuan Baldauf
2002-08-24 19:15 ` Chris Mason
2002-09-04 11:39 ` Xuan Baldauf
2002-09-04 12:13 ` Oleg Drokin
2002-08-25 21:21 ` Matthias Andree
2002-08-26 6:02 ` Valdis.Kletnieks
2002-08-25 21:20 ` Matthias Andree
2002-08-26 11:27 ` Hans Reiser
[not found] ` <20020905035604.GB6004@tapu.f00f.org>
2002-09-05 10:39 ` Hans Reiser [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 16:24 Xuan Baldauf
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=3D773457.6050601@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=cw@f00f.org \
--cc=green@namesys.com \
--cc=xuan--reiserfs@baldauf.org \
--cc=zam@thebsh.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.