public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dmitri Nikulin <dnikulin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ssd optimised mode
Date: Mon, 23 Feb 2009 11:40:29 -0500	[thread overview]
Message-ID: <yq1wsbht8ci.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <3a7f57190902221706l34e8f925m9ef687c1df920123@mail.gmail.com> (Dmitri Nikulin's message of "Mon\, 23 Feb 2009 12\:06\:38 +1100")

>>>>> "Dmitri" == Dmitri Nikulin <dnikulin@gmail.com> writes:

Dmitri> That's excellent, but until consumer-level drives have the same
Dmitri> feature, the fact remains that consumer SSDs are a net loss in
Dmitri> reliability compared to consumer rotating disks,

My SSD testing has not been very promising in the data integrity
department.  I've got a couple of drives here which end up corrupting
stuff every time they are reset or lose power.

"Stuff" in this case is on the order of megabytes, not a few sectors
like on spinning media.  With disk drives the risk of garbling unrelated
files is there but relatively small.  On SSDs it's much higher because
of the big blocking and the high latency erase/rewrite cycle.  In
several cases I've lost system binaries that obviously weren't being
written when I crashed the system.  In one case I even lost all of
/sbin.


Dmitri> I'm just curious if there's anything that can be done in a
Dmitri> filesystem to minimise the damage of a lost eraseblock.

The problem is that we have no way of knowing what's inside each erase
block.  We don't even know how big the erase block is.

-- 
Martin K. Petersen	Oracle Linux Engineering


  parent reply	other threads:[~2009-02-23 16:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 11:26 ssd optimised mode srimugunthan dhandapani
2009-02-20 16:01 ` Josef Bacik
2009-02-20 16:30   ` Chris Mason
2009-02-22  1:07     ` Dmitri Nikulin
2009-02-22 17:44       ` Steven Pratt
2009-02-23  1:06         ` Dmitri Nikulin
2009-02-23  1:22           ` Dongjun Shin
2009-02-23  2:33             ` Dmitri Nikulin
2009-02-23  3:15               ` Dongjun Shin
2009-02-23  3:17               ` Seth Huang
2009-02-23  4:01                 ` Dmitri Nikulin
2009-02-23  9:31                 ` Oliver Mattos
2009-02-23 16:40           ` Martin K. Petersen [this message]
2009-02-23 16:48             ` Claudio Martins
2009-02-23 17:23               ` Martin K. Petersen
2009-02-23 14:33       ` Chris Mason
2009-02-24  0:16         ` Dmitri Nikulin
2009-02-24  0:35           ` Dongjun Shin
2009-02-24  2:32           ` Martin K. Petersen
2009-02-24  3:53             ` Dmitri Nikulin
2009-02-24  4:09               ` Dongjun Shin
2009-02-24  4:10               ` Martin K. Petersen
2009-02-24  4:23                 ` Dmitri Nikulin
2009-02-23 22:19       ` Wes Felter

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=yq1wsbht8ci.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=dnikulin@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox