From: Alexander Tomokhov <alexoundos@ya.ru>
To: Kai Krakow <hurikhan77@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Is it possible to have metadata-only device with no data?
Date: Tue, 14 Feb 2017 04:22:27 +0300 [thread overview]
Message-ID: <1609461487035347@web31j.yandex.ru> (raw)
In-Reply-To: <20170205232721.165e96f3@jupiter.sol.kaishome.de>
Yeah, thank you for suggestion. Bcache is what I actually use right now. However it's concept is different, operating at block/bucket level and requires another (underlying!) layer.
06.02.2017, 01:27, "Kai Krakow" <hurikhan77@gmail.com>:
> Am Mon, 06 Feb 2017 00:42:01 +0300
> schrieb Alexander Tomokhov <alexoundos@ya.ru>:
>
>> Is it possible, having two drives to do raid1 for metadata but keep
>> data on a single drive only? --
>
> No, but you could take a look into bcache which should get you
> something similar if used in write-around mode.
>
> Random access will become cached in bcache, which should most of the
> time be metadata, plus of course randomly accessed data from HDD. If
> you reduce the sequential cutoff trigger in bcache, it should cache
> mostly metadata only.
>
> --
> Regards,
> Kai
>
> Replies to list-only preferred.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-14 1:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 21:42 Is it possible to have metadata-only device with no data? Alexander Tomokhov
2017-02-05 21:55 ` Hans van Kranenburg
2017-02-05 23:54 ` Roman Mamedov
2017-02-14 1:20 ` Alexander Tomokhov
2017-02-06 4:26 ` Duncan
2017-02-06 12:37 ` Austin S. Hemmelgarn
2017-02-05 22:27 ` Kai Krakow
2017-02-14 1:22 ` Alexander Tomokhov [this message]
2017-02-06 18:39 ` Omar Sandoval
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=1609461487035347@web31j.yandex.ru \
--to=alexoundos@ya.ru \
--cc=hurikhan77@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 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.