All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Chan <chrisfz@netvigator.com>
To: David Masover <ninja@slaphack.com>, reiserfs-list@namesys.com
Subject: Re: Which version will be merged into mainline kernel?
Date: Tue, 14 Nov 2006 18:03:00 +0800	[thread overview]
Message-ID: <45599454.1070701@netvigator.com> (raw)
In-Reply-To: <455986CB.6010608@slaphack.com>


> So, you have to have a way to insure data integrity beyond flushing it 
> to disk. Flushing it to disk is just a bit of unneeded integrity, that 
> costs a little bit of performance, and would probably save your ass in 
> one or two edge cases, but those cases shouldn't normally happen, and if 
> you're properly prepared for the hardware failing, you're properly 
> prepared for those edge cases, also.

fsync costs a lot of performance. Disk I/O is orders of magnitude off 
RAM. Anyway I guess you are smarter than Hans then since you obviously 
feel that his use of fsync is a bit of unneeded integrity.

> 
> 
> Anyway, this rant went on longer than I wanted it to, but since I've 
> brought it down to a question of economics, I don't really know the 
> answer. I do think, however, that arguing always for or against fsync is 
> absolutist and ultimately wrong.

Obviously we should take this question of fsync to its creator and all 
those who use it since they are all crippling their software 
implementing this dreadful useless function and actually making use of it.

> 
> 
>>> Anyway, are we done here? I don't think I disagree with your points, 
>>> maybe just your absolutism.
>>
>> Ha! Got tell that to a bank or any body who uses a database to store 
>> important data. Hans knows what he is doing providing data guarantee 
>> with fsync.
> 
> Yes, he's providing warm fuzzies for the banks. What are the banks doing 
> about hard disk failure? Remember, fsync only guarantees the data was 
> successfully written to a physical media -- it doesn't guarantee the 
> data will still be there when you want to go read it.

How could I ever forget that banks use unreliable media?

> 
> I won't speculate on Hans' opinions on whether fsync is really a good 
> design decision -- at least, not without him able to respond.

You don't have to. He did not create fsync and so you don't have to 
worry about whether fsync is a good design decision.

  parent reply	other threads:[~2006-11-14 10:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16  9:50 Which version will be merged into mainline kernel? Clemens Eisserer
     [not found] ` <4533D788.3000406@namesys.com>
2006-10-17 21:14   ` Clemens Eisserer
2006-10-17 22:03     ` Maciej Sołtysiak
2006-11-01 13:24   ` Clemens Eisserer
     [not found]     ` <45495858.6020507@namesys.com>
2006-11-02  9:09       ` Clemens Eisserer
     [not found]         ` <454A2AB9.3060103@namesys.com>
2006-11-02 19:43           ` Clemens Eisserer
     [not found]             ` <454A596F.8070909@namesys.com>
2006-11-08  7:21               ` Clemens Eisserer
2006-11-08  9:15                 ` Francesco Biscani
2006-11-08 10:21                   ` Andreas Dilger
2006-11-08 14:33                     ` Clemens Eisserer
     [not found]                       ` <455297E9.1070000@netvigator.com>
2006-11-09 12:57                         ` Clemens Eisserer
2006-11-09 18:19                           ` Clemens Eisserer
2006-11-11 15:14                     ` Danny Milosavljevic
2006-11-11 19:28                       ` Valdis.Kletnieks
2006-11-13 21:27                         ` Danny Milosavljevic
2006-11-14  5:51                           ` Christopher Chan
2006-11-14  9:16                             ` Clemens Eisserer
2006-11-13  3:11                       ` Christopher Chan
     [not found]                         ` <45582353.3070709@slaphack.com>
2006-11-13  9:34                           ` Christopher Chan
2006-11-13 21:17                             ` Danny Milosavljevic
2006-11-14  5:54                               ` Christopher Chan
     [not found]                             ` <45589ECD.4070105@slaphack.com>
2006-11-14  6:01                               ` Christopher Chan
     [not found]                                 ` <455986CB.6010608@slaphack.com>
2006-11-14 10:03                                   ` Christopher Chan [this message]
     [not found]                                     ` <455A0E5A.9060404@slaphack.com>
2006-11-15  3:21                                       ` Christopher Chan
2006-11-15  8:47                                         ` Clemens Eisserer
2006-11-08 10:35                 ` Jindrich Makovicka

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=45599454.1070701@netvigator.com \
    --to=chrisfz@netvigator.com \
    --cc=ninja@slaphack.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.