From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs across a mix of SSDs & HDDs
Date: Wed, 02 May 2012 01:56:52 +0100 [thread overview]
Message-ID: <jnq0ok$vmp$1@dough.gmane.org> (raw)
In-Reply-To: <4FA052B0.30108@yahoo.co.uk>
On 01/05/12 22:16, sam tygier wrote:
> On 01/05/12 20:35, Martin wrote:
>
>> The idea is to gain the random access speed of the SSDs but have the
>> HDDs as backup in case the SSDs fail due to wear...
>
> Have you looked at the bcache project http://bcache.evilpiepirate.org/
Many thanks for that. See also the latest on:
http://news.gmane.org/gmane.linux.kernel.bcache.devel
Looks rather interesting, but also too scary to be let loose on real
users until tested beyond staging.
Excellent idea. Full kudos for further development!
Regards,
Martin
next prev parent reply other threads:[~2012-05-02 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:35 btrfs across a mix of SSDs & HDDs Martin
2012-05-01 21:16 ` sam tygier
2012-05-02 0:56 ` Martin [this message]
2012-05-02 2:22 ` Bardur Arantsson
2012-05-02 4:28 ` Fajar A. Nugraha
2012-05-02 5:00 ` Bardur Arantsson
2012-05-02 5:30 ` Fajar A. Nugraha
2012-05-02 14:00 ` Martin
2012-05-02 18:41 ` Duncan
2012-05-02 23:54 ` vivo75
2012-05-03 0:46 ` 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='jnq0ok$vmp$1@dough.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).