All of lore.kernel.org
 help / color / mirror / Atom feed
From: "sys.syphus" <syssyphus@gmail.com>
To: Bob Marley <bobmarley@shiftmail.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: I need to P. are we almost there yet?
Date: Sat, 3 Jan 2015 13:03:47 -0600	[thread overview]
Message-ID: <CAAe=sHVNcCfe-AVBZ1mJV+uYN3F+s6kVQTgv8htw-_WWnK+Q=w@mail.gmail.com> (raw)
In-Reply-To: <54A83A95.2070108@shiftmail.org>

>
> Which is really not bad, considering the chance that something gets corrupt.
> Already it is an exceedingly rare event. Detection without correction can be
> more than enough. Since always things have worked in the computer science
> field without even the detection feature.
> Most likely even your bank account and mine are held in databases which are
> located in filesystems or blockdevices which do not even have the corruption
> detection feature.
> And, last but not least, as of now a btrfs bug is more likely than hard
> disks' silent data corruption.
>
>

I think thats dangerous thinking and what has gotten us here.

The whole point of zfs / btrfs is that due to the current size of
storage, what was previously unlikely is now a statistical certitude.
In short, Murphy's law.

We are now using green drives and s3 fuse and shitty flash media, the
era of trusting the block device is over.

  reply	other threads:[~2015-01-03 19:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 18:56 I need to P. are we almost there yet? sys.syphus
2014-12-29 19:00 ` sys.syphus
2014-12-29 19:04   ` Hugo Mills
2014-12-29 20:25     ` sys.syphus
2014-12-29 21:50       ` Hugo Mills
2014-12-29 21:16   ` Chris Murphy
2014-12-30  0:20     ` ashford
     [not found]       ` <CALBWd85UsSih24RhwpmDeMjuMWCKj9dGeuZes5POj6qEFkiz2w@mail.gmail.com>
2014-12-30 17:09         ` Fwd: " Jose Manuel Perez Bethencourt
2014-12-30 21:44       ` Phillip Susi
2014-12-30 23:17         ` ashford
2014-12-31  2:45           ` Phillip Susi
2014-12-31 17:27             ` ashford
2014-12-31 23:38               ` Phillip Susi
2015-01-01  1:26               ` Chris Samuel
2015-01-01 20:12                 ` Roger Binns
2015-01-02  3:47                   ` Duncan
2015-01-02 13:42               ` Austin S Hemmelgarn
2015-01-02 17:45                 ` Brendan Hide
2015-01-02 19:41                   ` Austin S Hemmelgarn
2014-12-29 21:13 ` Chris Murphy
2015-01-03 11:34 ` Bob Marley
2015-01-03 13:11   ` Duncan
2015-01-03 18:53     ` Bob Marley
2015-01-03 19:03       ` sys.syphus [this message]
2015-01-03 18:55     ` sys.syphus
2015-01-04  3:22       ` Duncan
2015-01-04  3:54         ` Hugo Mills
2015-01-03 21:58     ` Roman Mamedov
2015-01-04  3:24       ` Duncan

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='CAAe=sHVNcCfe-AVBZ1mJV+uYN3F+s6kVQTgv8htw-_WWnK+Q=w@mail.gmail.com' \
    --to=syssyphus@gmail.com \
    --cc=bobmarley@shiftmail.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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.