From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [10.34.131.78] (dhcp131-78.brq.redhat.com [10.34.131.78]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u11EJMSf008204 for ; Mon, 1 Feb 2016 09:19:22 -0500 References: From: Zdenek Kabelac Message-ID: <56AF696A.30503@redhat.com> Date: Mon, 1 Feb 2016 15:19:22 +0100 MIME-Version: 1.0 In-Reply-To: Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] LVM generates wrong low_water_mark value in thin-pool's table 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 Dne 1.2.2016 v 10:17 M.H. Tsai napsal(a): > Hi, > > I found that the parameter of thin-pool's table might be > wrong. In kernel, the this parameter is the number of free blocks. However, > LVM commit 99237f0908d87592815f4bdf3c239e8a108e835c sets this value as the > number of USED blocks, according > to activation_thin_pool_autoextend_threshold_CFG. Is that a bug? Ok - looks like my fault when translating lvm2 threshold usage to thin-pool target threshold usage. Thanks for noticing Zdenek