I had a similar problem today when running *any* LVM tool, including vgbackup/restore, so I was basically unable to do anything with the LVM subsystem. The error message was:
Parse error at byte 5 (line 1): unexpected token
I managed to figure (by strace'ing the vgdisplay process) that it is caused by corrupted /etc/lvm/cache/.cache file (most likely fscked up after a crash I had). Solution: delete the .cache file and run vgdisplay or whatever and it is recreated. I have verified that the recreated file is identical to the one I had on backup media.
So it is not much of a bug, but just a cryptic error message. It'll be prudent to change it to something meaningful - or just plainly recreate the cache file in such case and stop whining.
I had a similar problem today when running *any* LVM tool, including vgbackup/restore, so I was basically unable to do anything with the LVM subsystem. The error message was:
Parse error at byte 5 (line 1): unexpected token
I managed to figure (by strace'ing the vgdisplay process) that it is caused by corrupted /etc/lvm/ cache/. cache file (most likely fscked up after a crash I had). Solution: delete the .cache file and run vgdisplay or whatever and it is recreated. I have verified that the recreated file is identical to the one I had on backup media.
So it is not much of a bug, but just a cryptic error message. It'll be prudent to change it to something meaningful - or just plainly recreate the cache file in such case and stop whining.