From: Wes Felter <wesley@felter.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: ssd optimised mode
Date: Mon, 23 Feb 2009 16:19:25 -0600 [thread overview]
Message-ID: <gnv7dd$drd$1@ger.gmane.org> (raw)
In-Reply-To: <3a7f57190902211707h37ff1478vdc0e5ffff66fa4da@mail.gmail.com>
Dmitri Nikulin wrote:
> In the ideal future where SSDs can be run without a flimsy hardware
> FTL
I don't think this is likely at all for the same reasons Chris gave.
> I've read that one of the potentially crippling limitations of ZFS is
> that even its reliability features depend largely on being able to
> perform atomic writes, which are currently impossible (?) on flash
> media where a block has to be erased before it can be updated, clearly
> not an atomic operation. Is there any solution to this that doesn't
> depend on a battery backup?
A COW write to a pre-erased block should be atomic. See TxFlash:
http://storagemojo.com/2009/01/17/transflash/
Wes Felter - wesley@felter.org
prev parent reply other threads:[~2009-02-23 22:19 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
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 [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='gnv7dd$drd$1@ger.gmane.org' \
--to=wesley@felter.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.