#WARNING QUICKBOOT SNAPSHOTS FREE#

I do not envy the poor Qnap support people who are helping deal with this situation because it is a gnarly problem. I've tried manually editing the transaction id to allow the repair to complete, but thin_repair is still not able to repair the metadata to a state where the volume can be activated.

Some of the repair steps attempted so far: After freeing up some space by removing the lv544 volume (no documentation anywhere what lv544 is, but it appears to be unused), lvconvert -repair vg1/tp1 still fails due to transaction id mismatch. LVM is not very resilient to running out of space and you will easily hose your LVM metadata in a way that may be hard or impossible to recover from. If you Google around, you will see it is a real nightmare to try to recover from LVM metadata corruption caused when running out of space. My main volume is only 26.86t - the rest is taken up by snapshots. I have 9 automatic LVM snapshots hanging out and taking up space in the volume group. This mechanism does not appear to work very well (or at all). QTS is supposed to automatically delete old snapshots when space gets low, and it is supposed to not create new snapshots if there is no space. Then metadata writes failed and the LVM metadata became corrupted. What happened was as writes were happening, the drive was happily allocating new blocks until the volume group was completely full. # vgs VG #PV #LV #SN Attr VSize VFree vg1 2 14 0 wz-n- 34.38t 0

#WARNING QUICKBOOT SNAPSHOTS FREE#

There was no more free space in the volume group: Poking around via ssh, I discovered the drive would not mount because the LVM metadata was corrupted. I foolishly restarted and my volumes would no longer mount, so the data is inaccessible. I only discovered this when I got a notification about 'possible metadata corruption, please contact customer service for repair.' The volume switched to read-only. I still had plenty of space in my volume (it was about 60% full), and there was no warning that space was running out. I have automatic snapshotting enabled, and got into a situation where the underlying storage got completely filled due to LVM snapshots. I'm at 10 days downtime now and have escalated with Qnap support, with no resolution in sight. I ran into a bad situation with my Qnap with snapshotting enabled.

Warning quickboot snapshots