linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ferry Toth <ftoth@exalondelft.nl>
To: linux-btrfs@vger.kernel.org
Subject: Re: Hot data tracking / hybrid storage
Date: Tue, 17 May 2016 06:27:14 +0000 (UTC)	[thread overview]
Message-ID: <nhedk2$dpq$1@ger.gmane.org> (raw)
In-Reply-To: 20160516010524.7e208f96@jupiter.sol.kaishome.de

Op Mon, 16 May 2016 01:05:24 +0200, schreef Kai Krakow:

> Am Sun, 15 May 2016 21:11:11 +0000 (UTC)
> schrieb Duncan <1i5t5.duncan@cox.net>:
> 
>> Ferry Toth posted on Sun, 15 May 2016 12:12:09 +0000 as excerpted:
>> 
<snip>
> 
> You can go there with only one additional HDD as temporary storage. Just
> connect it, format as bcache, then do a "btrfs dev replace". Now wipe
> that "free" HDD (use wipefs), format as bcache, then... well, you get
> the point. At the last step, remove the remaining HDD. Now add your
> SSDs, format as caching device, and attach each individual HDD backing
> bcache to each SSD caching bcache.
> 
> Devices don't need to be formatted and created at the same time. I'd
> also recommend to add all SSDs only in the last step to not wear them
> early with writes during device replacement.
> 
> If you want, you can add one additional step to get the temporary hard
> disk back. But why not simply replace the oldest hard disk with the
> newest. Take a look at smartctl to see which is the best candidate.
> 
> I went a similar route but without one extra HDD. I had three HDDs in
> mraid1/draid0 and enough spare space. I just removed one HDD, prepared
> it for bcache, then added it back and removed the next.
> 
That's what I mean, a lot of work. And it's still a cache, with 
unnecessary copying from the ssd to the hdd.

And what happens when either a hdd or ssd starts failing?

> --
> Regards,
> Kai
> 
> Replies to list-only preferred.



  reply	other threads:[~2016-05-17  6:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15 12:12 Hot data tracking / hybrid storage Ferry Toth
2016-05-15 21:11 ` Duncan
2016-05-15 23:05   ` Kai Krakow
2016-05-17  6:27     ` Ferry Toth [this message]
2016-05-17 11:32       ` Austin S. Hemmelgarn
2016-05-17 18:33         ` Kai Krakow
2016-05-18 22:44           ` Ferry Toth
2016-05-19 18:09             ` Kai Krakow
2016-05-19 18:51               ` Austin S. Hemmelgarn
2016-05-19 21:01                 ` Kai Krakow
2016-05-20 11:46                   ` Austin S. Hemmelgarn
2016-05-19 23:23                 ` Henk Slager
2016-05-20 12:03                   ` Austin S. Hemmelgarn
2016-05-20 17:02                     ` Ferry Toth
2016-05-20 17:59                       ` Austin S. Hemmelgarn
2016-05-20 21:31                         ` Henk Slager
2016-05-29  6:23                         ` Andrei Borzenkov
2016-05-29 17:53                           ` Chris Murphy
2016-05-29 18:03                             ` Holger Hoffstätte
2016-05-29 18:33                               ` Chris Murphy
2016-05-29 20:45                                 ` Ferry Toth
2016-05-31 12:21                                   ` Austin S. Hemmelgarn
2016-06-01 10:45                                   ` Dmitry Katsubo
2016-05-20 22:26                     ` Henk Slager
2016-05-23 11:32                       ` Austin S. Hemmelgarn
2016-05-16 11:25 ` Austin S. Hemmelgarn

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='nhedk2$dpq$1@ger.gmane.org' \
    --to=ftoth@exalondelft.nl \
    --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).