Increased size thin pool lvm volume not seen in lsblk

Solution In Progress - Updated -

Issue

When using lvm2 with 16GB (max size) of thin-pool metadata, several operations are not combining well together.

It is allowed to create bigger metadata LV then the size accepted by kernel which does require to not pass bigger device - otherwise messages are thrown back to user from kernel.

Problem could be easily seen when user is passing 16GB LV to thin_restore and then using this 'restored' LV via lvconvert as a thin-pool metadata LV.

Version-Release number of selected component 2.02.169

Environment

  • Red Hat Enterprise Linux 7.4
  • lvm2 Thin provisioning
  • lvm2-2.02.166-1.el7_3.4.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content