Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: sftf <sftf-misc@mail.ru>
To: Stephan von Krawczynski <skraw@ithnet.com>, linux-btrfs@vger.kernel.org
Subject: Re[2]: Some very basic questions
Date: Tue, 28 Oct 2008 09:45:51 +0600	[thread overview]
Message-ID: <255283383.20081028094551@mail.ru> (raw)
In-Reply-To: <20081027164352.f7e39d1e.skraw@ithnet.com>

>> In my opinon, the whole thing comes up from the idea of using cheap hardware
>> and out-of-the-box configurations to keep promises of reliability and 
>> availability which are not realistic. There is a reason why there are more 
>> expensive HDDs, RAIDs, SANs with volume mirroring, multipathing and so on. 
>> Simply ignoring the fact that you have to use the proper tools to address 
>> specific problems and pray to the toothfairy to put a 
>> solve-all-my-problems-fs under your pillow is no solution. I'd rather have a 
>> solid fs with deterministic behavior and some state-of-the-art features.

SvK> Well, sorry to say, but I begin to sound a bit like Joseph Stiglitz
SvK> trying to explain why neoliberalism does not work out.
SvK> Please accept that this world is full of failure of all kinds. If you deny
SvK> that all your models and ideas will only be failures, too.
SvK> All I am saying is that we should accept that dead sectors, braindead
SvK> firmware-programmers, production in jungle-environment, transportation in
SvK> rough areas, high temperatures, high humidity, harddisks that have no disks
SvK> and so on are facts of live. And only a childs answer can be : "oops"
SvK> (sorry could not resist this one ;-)
 
+1000
Systems should survive and function or it's dead - like in nature.


      reply	other threads:[~2008-10-28  3:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 14:35 Some very basic questions dbz
2008-10-27 15:43 ` Stephan von Krawczynski
2008-10-28  3:45   ` sftf [this message]

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=255283383.20081028094551@mail.ru \
    --to=sftf-misc@mail.ru \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox