From: "A. James Lewis" <james@fsck.co.uk>
To: linux-bcache@vger.kernel.org
Subject: Re: layering question.
Date: Tue, 04 Aug 2015 18:16:02 +0100 [thread overview]
Message-ID: <55C0F352.8080602@fsck.co.uk> (raw)
In-Reply-To: <20150804190107.Horde.CuYUHXjE-ddVDzpxOLcbbPH@www3.nde.ag>
Thanks for the details... to clarify, you are using raid1 for SSD cache
devices, and then creating a RAID6 MD device to act as backing store?
What kernel are you using? You are having some stability issues, but in
principle it works?... what is performance like?
James
On 04/08/15 18:01, Jens-U. Mozdzen wrote:
> Hi James,
>
> Zitat von "A. James Lewis" <james@fsck.co.uk>:
>> Hi all...
>>
>> I've heard rumours that layering bcache with other block device
>> drivers might not be recommended... I wonder what the truth really
>> is... perhaps someone can advise.
>
> to me it's more than rumors. We're facing severe difficulties (server
> reboots, disks marked faulty by MDRAID, hangs) in our layered setup:
>
> - physical disks MD-RAID6 (data) plus two SSDs MD-RAID1 (cache)
> - bcache
> - LVM
> - DRBD for many of the logical volumes (always primary, no fail-overs)
> - ext4 fs
> - NFS / Samba / SCST (fileio)
>
>> I was planning to use 2 SSD's... combined with 4 large spinning
>> drives to create a large filesystem with BTRFS... my questions are
>> as follows.
>>
>> 1. Is there a way to use 2 SSD's directly, or would it be OK to use
>> MD to stripe them?... then used the MD array as the cache device?
>
> MD-RAID1 is what our current configuration looks like. We've also
> combined the spinning disks into a RAID6.
>
>> 2. I would be using BTRFS, so would it be better to create 4 separate
>> bcache devices each attached to the single cache device, and then use
>> BTRFS to raid 4 bcache devices... obviously this would be more
>> flexible, or would I need to make an MD raid of the 4 devices, and
>> then use that to create a single bcache device and build a BTRFS
>> filesystem on top of that.
>
> I have no btrfs experience, so I cannot answer that one. I went for a
> single data and cache device (via RAID) so I won't have to partition
> my SSDs - that would not have been scalable (we're planning to add
> plenty of physical disks over time, and to use many LVs/file systems).
>
>> Also, there's talk about a pending on-disk cache format change some
>> time around 3.19, but no details... is this over with, or still pending?
>
> Someone else might want to help with that one as well?
>
> Regards,
> Jens
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bcache" 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:[~2015-08-04 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 16:20 layering question A. James Lewis
2015-08-04 17:01 ` Jens-U. Mozdzen
2015-08-04 17:16 ` A. James Lewis [this message]
2015-08-05 6:56 ` Jens-U. Mozdzen
2015-08-05 6:28 ` Kai Krakow
2015-08-05 7:04 ` Jens-U. Mozdzen
2015-08-05 23:10 ` Kai Krakow
2015-08-06 0:54 ` A. James Lewis
2015-08-06 23:12 ` Kai Krakow
2015-08-07 12:43 ` Jens-U. Mozdzen
2015-08-07 14:38 ` A. James Lewis
2015-08-07 15:36 ` Jens-U. Mozdzen
2015-08-07 16:16 ` A. James Lewis
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 16:24 Jens-U. Mozdzen
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=55C0F352.8080602@fsck.co.uk \
--to=james@fsck.co.uk \
--cc=linux-bcache@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