From: Paul B. Henson <henson@acm.org>
To: lvm-devel@redhat.com
Subject: cache support
Date: Tue, 11 Feb 2014 13:04:08 -0800 [thread overview]
Message-ID: <0fff01cf276c$d059c8d0$710d5a70$@acm.org> (raw)
In-Reply-To: <A2CE00CC-6439-4A2E-A694-8E3B2656867B@redhat.com>
> From: Brassow Jonathan
> Sent: Tuesday, February 11, 2014 9:24 AM
>
> What do you think about caching a thin pool? Then you would get the
> benefit of caching for all of your LVs and you would get all the benefits
of
> thin and thin snapshots.
Hmm, I'm not that familiar with thin allocation in lvm. Basically, I would
allocate the entire PV as a thin LV, attach my entire cache to that, and
then create all of my production LV's with thin allocation out of the single
thin LV? Interesting thought. I have sufficient storage for at least the
midterm, my perhaps flawed understanding is that going with thin LV's
introduces an extra layer of complexity and inefficiency versus regular
allocation?
next prev parent reply other threads:[~2014-02-11 21:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 1:51 cache support Paul B. Henson
2014-02-05 7:35 ` Oliver Rath
2014-02-05 20:12 ` Paul B. Henson
2014-02-05 9:35 ` Zdenek Kabelac
2014-02-05 20:20 ` Paul B. Henson
2014-02-05 21:29 ` Zdenek Kabelac
2014-02-06 1:36 ` Paul B. Henson
2014-02-11 17:24 ` Brassow Jonathan
2014-02-11 21:04 ` Paul B. Henson [this message]
2014-02-12 17:39 ` Brassow Jonathan
2014-02-17 22:12 ` Paul B. Henson
2014-03-11 23:54 ` Paul B. Henson
2014-03-17 15:56 ` Brassow Jonathan
2014-03-18 1:07 ` Paul B. Henson
2014-03-29 1:38 ` Paul B. Henson
2014-03-29 1:43 ` Paul B. Henson
2014-04-02 20:34 ` Brassow Jonathan
2014-04-03 2:54 ` 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='0fff01cf276c$d059c8d0$710d5a70$@acm.org' \
--to=henson@acm.org \
--cc=lvm-devel@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 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.