Hide Forgot
Monitor the kernel's thin pool metadata usage, and it exceeds a specified threshold, extend it.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
QE reviewed this BZ for QA_ACK but was unable to ack due to a lack of requirements or description of how the new feature is supposed to work or be tested. Please see https://wiki.test.redhat.com/ClusterStorage/WhyNoAck
QA planning phase ends Aug 10th (tomorrow), without more information this feature will likely be nacked by QA. https://engineering.redhat.com/program/rhel/rhel-6-4-0/
While we have the preliminary testing code for lvm part the kernel part is still not finished. So the test for this bugzilla should focus on testing corner-case behavior when metadata device will get full. In the ideal case the pool should switch itself into read-only mode and data stored in pool should remain readable while any new write should fail.
Adding QA ack for 6.4. Devel will need to provide unit testing results however before this bug can be ultimately verified by QA.
Feature is not yet ready, postponing to the next release.
Monitoring of metadata volumes and its automatic online resize should be available with version 2.02.106 and newer and thin-pool target >=1.10 It's controlled with lvm.conf global/thin_pool_autoextend_threshold option.