[linux-lvm] thin: 235:2 pool target (735616 blocks) too small: expected 809216

Zdenek Kabelac zdenek.kabelac at gmail.com
Thu Jun 2 19:32:03 UTC 2016

Dne 2.6.2016 v 21:27 Brian J. Murrell napsal(a):
> On Thu, 2016-06-02 at 14:15 +0200, Zdenek Kabelac wrote:
>> Yep that might explain 'missing' surrouding details...
>> Basically any write might result in thin-pool running out of
>> threshold
>> and requireing new space
> Ahhh.  I was wondering if the resize in question could be some kind of
> implicit resizing done by the "hidden" thin-pool maintenance.  I'm
> fairly sure he knows zilch about LVM and resizing.  :-)

When lvm.conf  has defined thin_pool_autoextend_threshold <100% the pool is 
automatically monitored and resized when threshold is crossed.

>>  - what's unclear is the later failure which
>> would be really good to know....
> Is there anything in particular I can look for in the logs that would
> indicate when this implicit resizing was happening to look for other

If you spot any 'device-mapper' errors on May 25 in kernel log....

activity that might have caused a problem?
>> Ops  - so once again ;)
> Cheers.  :-)
> b.


More information about the linux-lvm mailing list