Search results

Turns out my case had nothing to do with BIOS setting. Filing up the metadatapool and running `lvconvert --repair` corrupted everything. I used the thin-provisioning-tools (https://github.com/jthornber/thin-provisioning-tools) and some advice from knowledgeable folks to recover. I documented...

It turns out filing up the metadatapool and running `lvconvert --repair` corrupted everything. I used the thin-provisioning-tools (https://github.com/jthornber/thin-provisioning-tools) and some advice from knowledgeable folks to recover. I documented the process here...

It turns out filing up the metadatapool and running `lvconvert --repair` corrupted everything. I used the thin-provisioning-tools (https://github.com/jthornber/thin-provisioning-tools) and some advice from knowledgeable folks to recover. I documented the process here...

Were you ever able to get this fixed? I just ran into a similar issue after filling up my metadata pool. I started seeing LVM issues and I tried to grow the pool size. Since I suspected the metadata was corrupted I tried the below which brought me to your start. lvconvert --repair I cannot...

Mark, I know this was over 2 years ago but did you ever figure out what happened? I'm not sure overcommitting was your problem. I just ran into something very similar. My metapool filled and I started getting all kinds of error. I was able to extend it and reboot but it seems pve/data, the thin...

Daniel, could you elaborate on the BIOS setting? Are you talking about the PVE host? I ran into the same issue. Filed up the metadata pool, did the repair and right now I can activate the pve/data but not any of the thin provisioned volumes: lvchange -ay pve/vm-100-disk-5 device-mapper...