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: Mon, 13 Nov 2006 17:34:59 +0800 [thread overview]
Message-ID: <45583C43.5070904@netvigator.com> (raw)
In-Reply-To: <45582353.3070709@slaphack.com>
David Masover wrote:
> Christopher Chan wrote:
>> Danny Milosavljevic wrote:
>
>>> The only possibility one could still lose mail when having proper
>>> hardware failsafes would be if the kernel had a bug and crashed (and
>>> that's
>>> so bad, it doesn't really warrant any working around it).
>> Ever used DOS with smartdrv? smartdrv gave a performance boost by
>> storing recently touched files in memory and writing to disk later. This
>> is called a disk cache. You would be explicitly told to NOT just turn
>> off the computer each time smartdrv was loaded. You had to first clear
>> the cache and then you could power off the box otherwise you would lose
>> any data sitting in the cache that had not been flushed.
>
> Which means that, if you have proper hardware failsafes, you will only
> lose data if you don't properly clear the cache before shutting down
> (which Linux shutdown scripts will do for you), or if there's a crash.
> I'm sure many people used smartdrv without problems, and appreciated the
> performance boost.
Which is why data important software use fsync/fsyncdata to minimize
data loss from crashes.
>
> Moral of the story: Data loss is a Bad Thing. Those who would give up
> essential data safety for a little temporary performance deserve
> neither. (With apologies to Ben Franklin.)
>
> And while reading this, it's important to keep in mind that I do not
> practice what I've just preached. I'm addicted to the performance, and I
> 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.
next prev parent reply other threads:[~2006-11-13 9:34 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 [this message]
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
[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=45583C43.5070904@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.