From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Douglas Paul <doug@bogon.ca>
Subject: Re: [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB
Date: Mon, 21 Jan 2019 21:19:52 +0100 [thread overview]
Message-ID: <a909ea33-ab62-e637-d3c1-66ad70bd87ed@redhat.com> (raw)
In-Reply-To: <20180718145810.GF12563@bogon.ca>
Dne 18. 07. 18 v 16:58 Douglas Paul napsal(a):
> On Wed, Jul 18, 2018 at 03:25:10PM +0100, Ryan Launchbury wrote:
>> Does anyone have any other ideas or potential workarounds for this issue?
>>
>> Please let me know if you require more info.
>
> I didn't see this in the previous messages, but have you tried temporarily
> remounting the filesystems read-only if you can't unmount them?
>
> Also, earlier you mentioned looking at /var/log/dmesg for write errors. On
> my systems, that only contains a snapshot at boot. I have to run dmesg to
> see the latest updates. It seems suspicious to have nothing in the dmesg
> during 61 days past 10 seconds after system boot ...
>
Hi
So this should help:
lvchange --cachesettings migration_threshold=16384 vg/cacheLV
the problem was the usage of unexpectedly big chunk sizes,
that are used when cache-pool size is big (>TiB) and chunksizes
are >= 1MiB.
Upstream has committed patches for automatic protection against too small
migration threshold.
Zdenek
prev parent reply other threads:[~2019-01-21 20:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 9:18 [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB Ryan Launchbury
2018-06-20 10:15 ` Zdenek Kabelac
2018-06-20 11:10 ` Ryan Launchbury
2018-06-22 18:13 ` Gionatan Danti
2018-06-22 19:22 ` Ryan Launchbury
2018-06-22 20:07 ` Zdenek Kabelac
2018-06-23 10:09 ` Gionatan Danti
2018-06-24 19:18 ` Ryan Launchbury
2018-06-25 17:19 ` Gionatan Danti
2018-06-25 17:20 ` Ryan Launchbury
2018-06-25 17:40 ` Gionatan Danti
2018-07-18 14:25 ` Ryan Launchbury
2018-07-18 14:58 ` Douglas Paul
2019-01-21 20:19 ` 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=a909ea33-ab62-e637-d3c1-66ad70bd87ed@redhat.com \
--to=zkabelac@redhat.com \
--cc=doug@bogon.ca \
--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).