From mboxrd@z Thu Jan 1 00:00:00 1970 References: <66e4dbc1-ca00-3abf-5100-d19f7439a281@magenta.tv> <6e53a6f7-9896-2905-92ad-6b9c36f565ab@redhat.com> <39a2408c600ed4caf00724eb72c191c2@assyoma.it> <326c998e-67f8-6331-c8f1-a22e8c06fd98@redhat.com> <213e498ea447f141c7a975c13416281e@assyoma.it> <880611df631d8ad243b8c2974102bce8@assyoma.it> <6946bbe9-3073-da99-b7d1-bceb978344a3@magenta.tv> <20180718145810.GF12563@bogon.ca> From: Zdenek Kabelac Message-ID: Date: Mon, 21 Jan 2019 21:19:52 +0100 MIME-Version: 1.0 In-Reply-To: <20180718145810.GF12563@bogon.ca> Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LVM general discussion and development , Douglas Paul 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