[linux-lvm] metadata device too small
listac at nebelschwaden.de
Mon Jan 13 21:29:07 UTC 2020
Sorry, did by mistake answer privately, not to the list.
Am 13.01.20 um 22:27 schrieb Ede Wolf:
> unfortunately, as everything looked all right after the swap, I've
> deleted the too big metadata pool.
> Should have tried to actually mount the LVs, but as they where online
> and not errors reported, I proceeded.
> Just while trying to rezise (where the big pool had to go, as otherwise
> I would not have had the space to resize) I ran across the transaction
> ID error. That even did not look fatal, until I noted, nothing has
> So now I have one pool with the transaction ID error, that upon after
> manual fixing claims no data available, and two "repaired" versions of
> that metadatapool.
> Am 13.01.20 um 20:11 schrieb Zdenek Kabelac:
>> Dne 13. 01. 20 v 17:35 Ede Wolf napsal(a):
>>> Hello Marian,
>>> thanks for that advice, but my thin-provisioning-tools already are
>>> at version 0.8.5
>>> Basically I consider the data now lost.
>> Why do you think they are lost ?
>> Don't you have any 'valid' LV with metadata ?
>> You can use your 'too big' metadava LV and 'thin_repair' it to
>> appropritely sized one - it should work easily.
>> linux-lvm mailing list
>> linux-lvm at redhat.com
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
More information about the linux-lvm