Hey guys,
I'm at a loss here. I recently moved from other virtualization solutions to Proxmox and have been pretty happy. Glad I made the switch…
One thing that has got me stumped is this: a few days a go I got 2 enterprise-grade SSDs for VM storage. I was using a "consumer" SSD for that, and it was working fine, but I wanted some safety. I installed the 2 SSDs, got them configured in a mirror with ZFS. To begin, and because I needed to remove the other SSD to be able to install the 2 new ones, I moved all the VMs and containers to a spinning drive (worked fine). After removing the other SSD and getting the new ones up and running, I started moving the VMs and containers to the new storage. I added the new pool (volData) to PVE and configured it with "thin provision". The VMs moved fine (as zvols, which is nice) but I could not move the containers. It kept telling me: TASK ERROR: cannot open directory //volData: No such file or directory. I tried creating a dataset (volData/pve) and add that as an additional storage for containers and that gave me the same exact error message. I'm really confused as to what is going on here. My next step would be to manually create a zvol, format it as ext4 and add that as a directory in PVE. I'm sure that'll work, but I'm really confused as to why adding the regular ZFS pool or dataset isn't working… I read somewhere that using directories in ZFS and not ZFS "proper" is not really the best solution.
Also, why doesn't PVE allow me to add a ZFS dataset and set it for backups? Why just images and containers?
Thanks for the help.
I'm at a loss here. I recently moved from other virtualization solutions to Proxmox and have been pretty happy. Glad I made the switch…
One thing that has got me stumped is this: a few days a go I got 2 enterprise-grade SSDs for VM storage. I was using a "consumer" SSD for that, and it was working fine, but I wanted some safety. I installed the 2 SSDs, got them configured in a mirror with ZFS. To begin, and because I needed to remove the other SSD to be able to install the 2 new ones, I moved all the VMs and containers to a spinning drive (worked fine). After removing the other SSD and getting the new ones up and running, I started moving the VMs and containers to the new storage. I added the new pool (volData) to PVE and configured it with "thin provision". The VMs moved fine (as zvols, which is nice) but I could not move the containers. It kept telling me: TASK ERROR: cannot open directory //volData: No such file or directory. I tried creating a dataset (volData/pve) and add that as an additional storage for containers and that gave me the same exact error message. I'm really confused as to what is going on here. My next step would be to manually create a zvol, format it as ext4 and add that as a directory in PVE. I'm sure that'll work, but I'm really confused as to why adding the regular ZFS pool or dataset isn't working… I read somewhere that using directories in ZFS and not ZFS "proper" is not really the best solution.
Also, why doesn't PVE allow me to add a ZFS dataset and set it for backups? Why just images and containers?
Thanks for the help.