Search results

Must have been a fluke, did it again and it seems to have cleaned up this time... This seems to be the trick to take care of the volumes and volume groups I was mounting (will be specific to your LVM config so don't copy verbatim). This also assumes you don't use LVM normally, otherwise this...

Can't figure out what's holding it open. Rebooting released it, but obviously I'd like to avoid that in the future. I'm sure it has something to do with LVM but I couldn't see how it was being held busy.

Well... It works until you delete the vm... then the zfs volume won't delete no matter what you do... root@pve:/tmp# pvesm free local-zfs:vm-921-disk-0 zfs error: cannot destroy 'rpool/data/vm-921-disk-0': dataset is busy root@pve:/tmp# grep vm-921-disk-0 /proc/*/mounts root@pve:/tmp#...

And then to gracefully unmount and remove... Looks something like: lvchange -an /dev/vg-db-vda/* vgchange -an vg-db-vda dmsetup remove vm-921-disk-0p3 I tried to do just vgchange -an vg-db-vda but it didn't seem to work. The disk in dmsetup remove was found by running dmsetup ls

Yeah, that's 1000x better. Thanks!

For starters, the zfs devices are excluded from lvm (which I mean makes sense, who would do this normally). /etc/lvm/lvm.conf: devices { # added by pve-manager to avoid scanning ZFS zvols global_filter=["r|/dev/zd.*|"] } And there's no reason to change that. I ended up...

I have a guest which uses a zfs-local volume. On that guest, is a partition 3 partitions, one of them is an LVM partition/volume group. And that volume group contains several volumes, one of them I want to modify OUTSIDE of the virtual. I basically need to inject some files before the first boot...

I have a Linux container which has an interface which acts as a bridge to ioulive86 (https://github.com/jlgaddis/ioulive86). Its function is to bridge Virtual Routers to interfaces (in this case an interface of an LXC container). I wanted to use VM firewall rules to give the ability to lock...