From: "Richard W.M. Jones" <rjones@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] Testing the new LVM cache feature
Date: Thu, 22 May 2014 16:22:32 +0100 [thread overview]
Message-ID: <20140522152232.GC14236@redhat.com> (raw)
In-Reply-To: <537E0D25.7010108@redhat.com>
Well I'm happy to experiment for you.
At the moment I'm stuck here:
# vgcreate vg_cache /dev/sdc1
Volume group "vg_cache" successfully created
# lvcreate -L 1G -n lv_cache_meta vg_cache
Logical volume "lv_cache_meta" created
# lvcreate -L 229G -n lv_cache vg_cache
Logical volume "lv_cache" created
# lvs
LV VG Attr LSize [...]
lv_cache vg_cache Cwi---C--- 229.00g
lv_cache_meta vg_cache -wi-a----- 1.00g
testoriginlv vg_guests -wi-a----- 100.00g
# lvconvert --type cache-pool --poolmetadata /dev/vg_cache/lv_cache_meta /dev/vg_cache/lv_cache
Logical volume "lvol0" created
Converted vg_cache/lv_cache to cache pool.
# lvs
LV VG Attr LSize [...]
lv_cache vg_cache Cwi---C--- 229.00g
testoriginlv vg_guests -wi-a----- 100.00g
# lvconvert --type cache --cachepool vg_cache/lv_cache vg_guests/testoriginlv
Unable to find cache pool LV, vg_cache/lv_cache
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It seems as if vg_cache/lv_cache is a "cache pool" but for some reason
lvconvert is unable to use it.
The error seems to come from this code:
if (!(cachepool = find_lv(origin->vg, lp->cachepool))) {
log_error("Unable to find cache pool LV, %s", lp->cachepool);
return 0;
}
Is it looking in the wrong VG?
Or do I have to have a single VG for this to work? (That's not made
clear in the documentation, and it seems like a strange restriction).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2014-05-22 15:22 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 [this message]
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
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=20140522152232.GC14236@redhat.com \
--to=rjones@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@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).