From: Christopher Chan <chrisfz@netvigator.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Which version will be merged into mainline kernel?
Date: Tue, 14 Nov 2006 14:01:32 +0800 [thread overview]
Message-ID: <45595BBC.6000602@netvigator.com> (raw)
In-Reply-To: <45589ECD.4070105@slaphack.com>
>> Which is why data important software use fsync/fsyncdata to minimize
>> data loss from crashes.
>
> If (and only if) you actually read and accepted the paragraph you're
> quoting there, the point is that using fsync and fdatasync on these is
> kind of like doing bad block relocation in software, when the hard disk
> is already doing it for you. There are situations where it's useful, but
> mostly, it's just a performance drain without a point.
You have no idea what fsync/fsyncdata does. They cannot be compared to
bad block relocation at all. That is an apples to oranges comparison.
>
> I don't necessarily agree with this point of view, but there you go.
>
>>> could probably argue the other side just as effectively. Besides, at
>>> least on my experimental/gaming rig, I like a little adrenaline in my
>>> admin work!
>>>
>>
>> Try arguing why you lost thousands of mails when the box crashed and
>> justifying it.
>
> There aren't thousands of mails on my experimental dev/gaming rig. Also,
> it hasn't crashed in a month or two (I seem to have upgraded/hacked my
> way out of its last major crasher), and it's running all kinds of
> experimental stuff. Sure, individual programs crash from time to time
> (especially my hacks), but that's irrelevant to the fsync discussion.
I was not referring to your gaming rig. Did you say that you don't use
fsync for your production boxes?
> So, as far as I can tell, this mailserver (that I'm sending this from
> right now), which is amd64/reiser4/no_fsync, hasn't lost a single
> message. And I don't even have an APM on it (although that reminds me, I
> need to buy one now, as in, "tomorrow" now.)
Heh. Just wait till you get a crash shortly after a write with fsync
disabled.
>
> 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. I was very surprised when I heard all those reports about
zero data loss on reiser4 boxes after a crash. Now I have an idea why.
next prev parent reply other threads:[~2006-11-14 6:01 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 [this message]
[not found] ` <455986CB.6010608@slaphack.com>
2006-11-14 10:03 ` Christopher Chan
[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=45595BBC.6000602@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.