From: Alasdair G Kergon <agk@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Testing the new LVM cache feature
Date: Fri, 30 May 2014 12:38:59 +0100 [thread overview]
Message-ID: <20140530113859.GB29705@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20140529204719.GD1302@redhat.com>
On Thu, May 29, 2014 at 09:47:20PM +0100, Richard W.M. Jones wrote:
> Is there a reason why fast and slow devices need to be in the same VG?
> I've talked to two other people who found this very confusing. No one
> knew that you could manually place LVs into different PVs, and it's
> something of a pain to have to remember to place LVs every time you
> create or resize one. It seems it would be a lot simpler if you could
> have the slow PVs in one VG and the fast PVs in another VG.
We recommend you use tags. Much more flexible/dynamic solution than forcing
the use of separate VGs.
pvchange --addtag ssd
pvs -o+tags
lvcreate ... $vg @ssd
to restrict the allocation the command performs to the PVs with the 'ssd' tag.
Alasdair
next prev parent reply other threads:[~2014-05-30 11:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 10:18 [linux-lvm] Testing the new LVM cache feature Richard W.M. Jones
2014-05-22 14:43 ` Zdenek Kabelac
2014-05-22 15:22 ` Richard W.M. Jones
2014-05-22 15:49 ` Richard W.M. Jones
2014-05-22 18:04 ` Mike Snitzer
2014-05-22 18:13 ` Richard W.M. Jones
2014-05-29 13:52 ` Richard W.M. Jones
2014-05-29 20:34 ` Mike Snitzer
2014-05-29 20:47 ` Richard W.M. Jones
2014-05-29 21:06 ` Mike Snitzer
2014-05-29 21:19 ` Richard W.M. Jones
2014-05-29 21:58 ` Mike Snitzer
2014-05-30 9:04 ` Richard W.M. Jones
2014-05-30 10:30 ` Richard W.M. Jones
2014-05-30 13:38 ` Mike Snitzer
2014-05-30 13:40 ` Richard W.M. Jones
2014-05-30 13:42 ` Heinz Mauelshagen
2014-05-30 13:54 ` Richard W.M. Jones
2014-05-30 13:58 ` Zdenek Kabelac
2014-05-30 13:46 ` Richard W.M. Jones
2014-05-30 13:54 ` Heinz Mauelshagen
2014-05-30 14:26 ` Richard W.M. Jones
2014-05-30 14:29 ` Mike Snitzer
2014-05-30 14:36 ` Richard W.M. Jones
2014-05-30 14:44 ` Mike Snitzer
2014-05-30 14:51 ` Richard W.M. Jones
2014-05-30 14:58 ` Mike Snitzer
2014-05-30 15:28 ` Richard W.M. Jones
2014-05-30 18:16 ` Mike Snitzer
2014-05-30 20:53 ` Mike Snitzer
2014-05-30 13:55 ` Mike Snitzer
2014-05-30 14:29 ` Richard W.M. Jones
2014-05-30 14:36 ` Mike Snitzer
2014-05-30 11:53 ` Mike Snitzer
2014-05-30 11:38 ` Alasdair G Kergon [this message]
2014-05-30 11:45 ` Alasdair G Kergon
2014-05-30 12:45 ` Werner Gold
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=20140530113859.GB29705@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=rjones@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).