Red Hat Bugzilla – Bug 905028
Avoid reading devices we know to fail
Last modified: 2016-10-11 18:56:43 EDT
Description of problem:
With lvm2 with have several cases, when we could skip reading/checking devices we may know we shouldn't read.
There are several scenarios were we are trying to i.e. check for metadata on devices, they are not readable or should not be scanned.
Here are 2 examples -
1st. activate thin pool device - scanning such volume has no use - since thin pool has no header - and thus it presents it self as a device with 'mixed' signatures - i.e. block zero could be from any thin volume which happend
to allocate this block - as well as the block at the end of this device.
2nd. reading invalid snapshot results in error read.
(Bug 839811 comment 6)
Both cases depend on the scan order - but if we know metadata ahead of touching
this device - we may potentially have good chance to skip scanning them.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This bug is getting to be more important since i.e. thin-pool might be in failed stated....
Scanning needs refinement.