linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [linux-lvm] Network-attached block storage and local SSDs for dm-cache
Date: Tue, 23 Apr 2019 12:20:13 +0200	[thread overview]
Message-ID: <9916e4a1-5c72-f30c-a58b-0542816d7158@redhat.com> (raw)
In-Reply-To: <20190419193036.GA24986@chatter.i7.local>

Dne 19. 04. 19 v 21:30 Konstantin Ryabitsev napsal(a):
> Hi, all:
> 
> I know it's possible to set up dm-cache to combine network-attached block 
> devices and local SSDs, but I'm having a hard time finding any first-hand 
> evidence of this being done anywhere -- so I'm wondering if it's because there 
> are reasons why this is a Bad Idea, or merely because there aren't many 
> reasons for folks to do that.
> 
> The reason why I'm trying to do it, in particular, is for mirrors.kernel.org 
> systems where we already rely on dm-cache to combine large slow spinning disks 
> with SSDs to a great advantage. Most hits on those systems are to the same set 
> of files (latest distro package updates), so dm-cache hit-to-miss ratio is 
> very advantageous. However, we need to build newest iterations of those 
> systems, and being able to use network-attached storage at providers like 
> Packet with local SSD drives would remove the need for us to purchase and host 
> huge drive arrays.
> 
> Thanks for any insights you may offer.


Hi

 From lvm2 POV - if you put both devices into single VG - you should be able 
to easily configure the setup in a way, that your 'main/origin' LV sitting on 
network storage and  cache is setup to be located on SSD.

lvcreate -LMAXSIZE --name MYLV vg  /dev/networkshdd
lvcreate --cache -Lcachesize  vg/MYLV  /dev/ssd

But of course as Mike points out - cache currently expects the origin device 
is reliable one.

Regards

Zdenek

      parent reply	other threads:[~2019-04-23 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 19:30 [linux-lvm] Network-attached block storage and local SSDs for dm-cache Konstantin Ryabitsev
2019-04-22 18:25 ` Mike Snitzer
2019-04-23 13:58   ` Konstantin Ryabitsev
2019-04-23 10:20 ` Zdenek Kabelac [this message]

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=9916e4a1-5c72-f30c-a58b-0542816d7158@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-lvm@redhat.com \
    /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).