Search results

A good way not to get confused with those double disks is to use dm-multipath. It handles the whole multipathing thing and exposes each physical device under/dev/mapper/<wwn>. Those devices can than be used with zfs or md or whatever as those system should not care about the underlying...

Thanks for the response. However after having a look at disks created via the Webinterface I realised that with my storage type "btrfs" the filename must have a fileending like .qcow2 See https://pve.proxmox.com/pve-docs/pvesm.1.html for available file types. So in the end this worked...

I'd like to use `pvesm alloc` but not matter what kind of filename I use is always returns the same error: root@host:~# pvesm alloc hdd_raid10_data01 100 foo 100G unable to parse volume filename 'foo' How is this tool supposed to work?

It its also always possible to manually add a disk as qemu parameter. Eg if your VM has the ID 100 and your disk is sdX you can add the following line in your config file under /etc/pve/qemu-server/100.conf: args: -drive file=/dev/sdX,if=virtio,index=10,format=raw Of course proxmox has no...