Long ago, Nostradamus foresaw that on 11/28/2012 08:57 AM, Zdenek
Kabelac would write:
>
>> To resurrect a really, really, old thread, did anything ever get done
>> in LVM2
>> to either automatically or manually map out PEs with bad blocks in them?
>>
>> Does anyone have a recipe for doing this -- to save me the time of
>> figuring it
>> all out for myself?
>
>
> Sorry, no automated tool.
>
> You could possibly pvmove separated PEs manually with set of pvmove
> commands.
> But I'd strongly recommend to get rid of such broken driver quickly
> then you loose any more data - IMHO it's the most efficient solution
> cost & time.
There are many situations where you are out with a laptop in a region
where there is no Fry's to purchase a new drive.  Often, such region
additionally impose stiff duties, many times the price, if you try to
order said drive online.  That's assuming internet is usable today in
said region.

So "replace the drive" might the best policy ideally, but is often
impossible for travellers in tech-primitive regions.

Having helped people in such situations (where internet at least was
working), I've used the attached script to help find affected LVs and files.