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>,
	Oliver Rath <rath@mglug.de>
Subject: Re: [linux-lvm] Howto change cachepolicy on cached thinpool devices?
Date: Mon, 15 May 2017 15:38:19 +0200	[thread overview]
Message-ID: <29e90a7a-e3ca-0dc0-93d2-7490bcef37c6@redhat.com> (raw)
In-Reply-To: <61de26b1-0849-e71f-133c-a8357b773ee9@mglug.de>

Dne 15.5.2017 v 15:25 Oliver Rath napsal(a):
> Hi list,
> 
> caching the _tdata part of a thinpool works fine now. Unfortunatly with
> lvchange it is not possible to change the policy (vg:dmivg,
> cachepool:dmipool,thinpool:winthinpool):
> 
> # lvchange --cachepolicy cleaner dmivg/dmicache
>    Operation not permitted on hidden LV dmivg/dmicache.
> 
> # lvchange --cachepolicy cleaner /dev/mapper/dmivg-winthinpool_tdata
>    Operation not permitted on hidden LV dmivg/winthinpool_tdata.
> 
> # lvchange --cachepolicy cleaner dmivg/winthinpool
>    Command on LV dmivg/winthinpool does not accept LV type thinpool.
> Required LV types are cache cachepool .
>    Command not permitted on LV dmivg/winthinpool.
> 
> The only possibility at the moment seems to change it via lowlewel
> dmsetup command.
> 
> # dmsetup status dmivg-winthinpool_tdata
> 0 7730954240 cache 8 1458/9216 128 720896/720896 4608761 7143953 1177059
> 5866353 40700 761596 2993 2 metadata2 writeback 2 migration_threshold
> 2048 smq 0 rw -
> 
> ...
> 
> How can this be done with lv*?

Hi

By opening BZ  at http://bugzilla.redhat.com/  for lvm2 ;)
Seem this has got lost in various code changes.

Should be easy to add this to supported variant.

Regards

Zdenek

  reply	other threads:[~2017-05-15 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 13:25 [linux-lvm] Howto change cachepolicy on cached thinpool devices? Oliver Rath
2017-05-15 13:38 ` Zdenek Kabelac [this message]
2017-05-15 16:02 ` David Teigland
2017-05-15 20:10   ` Oliver Rath

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=29e90a7a-e3ca-0dc0-93d2-7490bcef37c6@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=rath@mglug.de \
    /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).