All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Warr <jason@warr.net>
To: "Paul B. Henson" <henson@acm.org>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Another bcache hang
Date: Fri, 22 Nov 2013 14:34:22 -0600	[thread overview]
Message-ID: <528FBFCE.7020104@warr.net> (raw)
In-Reply-To: <156301cee7bc$3b7fc420$b27f4c60$@acm.org>


On 11/22/2013 01:51 PM, Paul B. Henson wrote:
>> From: Jason Warr [mailto:jason@warr.net]
>> Sent: Friday, November 22, 2013 6:35 AM
>>
>> As I start to use more LVM based RAID, and with it fault allocation
>> policy's, logically it makes more sense to setup individual volumes as
>> backing stores instead of PV's.  That way you always know your caching
>> the volumes you want no matter what PV device(s) they are sitting on.
> I looked at LVM raid once a while ago, it didn't really seem quite there
> yet. I haven't checked recently, do you consider it a better choice than
> classic md raid now? It would be one less layer in the stack, but mdraid has
> been pretty bulletproof for me for quite some time and I'd be hesitant to
> switch.
>

I would say it is going to be a better choice for use cases that are
more dynamic in nature.  By that I mean where you may have a larger
number of smaller volumes that may have different needs for redundancy
and/or where you may be adding or removing physical devices often.

LVM RAID, not to be confused with LVM mirroring or striping, gives you
more flexibility in extent placement than what you have if you use MD
RAID.  From what I understand the LVM RAID code comes directly from the
MD RAID code so it should be just as reliable as MD but give you more
volume level flexibility.  There is obviously some serious performance
constraints that can come up if you mix RAID types on the same set of
physical disks but this is one place where bcache can come in and help.

MD RAID will still be the option of choice for me in cases where I have
a single large volume that will span multiple PV's such as a multi
terabyte media repository.  Although since overall performance is not
terribly important for me there it may make more sense to just use LVM
RAID to keep it all in the same layer.

There are lots of good options that are becoming more viable now that we
have a real in kernel caching device to mask out allot of previous
performance concerns.

>
> --
> 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

  reply	other threads:[~2013-11-22 20:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 13:56 Another bcache hang David H. Rhodes Clymer
2013-11-22  1:07 ` Paul B. Henson
2013-11-22  3:49   ` David H. Rhodes Clymer
2013-11-22 14:35     ` Jason Warr
2013-11-22 19:51       ` Paul B. Henson
2013-11-22 20:34         ` Jason Warr [this message]
2013-11-22 23:52           ` Paul B. Henson
2013-11-23  0:38             ` Matthew Patton
2013-11-23  0:43               ` Paul B. Henson
2013-11-23  1:02             ` Jason Warr
2013-11-23  2:14               ` Paul B. Henson
2013-11-23  2:38                 ` Jason Warr
2013-11-22 19:46     ` Paul B. Henson

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=528FBFCE.7020104@warr.net \
    --to=jason@warr.net \
    --cc=henson@acm.org \
    --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 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.