Ok, so , fresh install of proxmox 4.0 release, root on ZFS mirror.I tried to create a container, googled 'Warning, had trouble writing out superblocks', found a thread here, and remembered I had to create a zfs store on 3.4 too.So, I've created a 'ZFS' storage in the gui, picking "rpool" (though there's a couple of sub choices under that too), left things on default, has images and containers selected in 'use for'I create a VM, I can pick ZFS, it's all fine. If I create a CT, I can't pick ZFS as the storage - only local, which then fails.Any ideas?I also tried deselecting 'containers' as a type for 'local'. However, I can't - whenever I deselect and hit ok, it re-adds it the next time I look.
ZFS + LXC issue - can't select the ZFS storage for a container
- Thread starter Beardydude
- Start date
I already did, I said that in my first post? 
Turns out rebooting the machine after creating the zfs store made it start working! I'd still like to know though: 1) why I cannot deselect containers from the local storage? I can and have deselected disk images as a type for local 2) which of the pre-created zfs pools in 4.0 I should be using for creating the zfs store - rpool, rpool/ROOT or rpool/ROOT/pve-1 - or is best practise to create a new zfs dataset and mount it somewhere else? and 3) with root on zfs as an install time option since 3.4, why it doesn't come with a pre-created default zfs storage now? Or why local itself isn't treated as ZFS (if it is) and usable as is?
Turns out rebooting the machine after creating the zfs store made it start working! I'd still like to know though: 1) why I cannot deselect containers from the local storage? I can and have deselected disk images as a type for local 2) which of the pre-created zfs pools in 4.0 I should be using for creating the zfs store - rpool, rpool/ROOT or rpool/ROOT/pve-1 - or is best practise to create a new zfs dataset and mount it somewhere else? and 3) with root on zfs as an install time option since 3.4, why it doesn't come with a pre-created default zfs storage now? Or why local itself isn't treated as ZFS (if it is) and usable as is?
Thats a bug
IMHO a separate dataset is a good start.
not implemented, but planned feature.
mostly because zfspool type cannot store iso/template/backups, so you normally need both types (but there are other reasons).
Cheers for the very helpful answers Roll on those proposed changes and I take it I don't need to report the bug anywhere if you read it?
Roll on those proposed changes and I take it I don't need to report the bug anywhere if you read it?yip I also cannot deselect containers - is their no config file I can do it on instead via shell?
Cheers for the very helpful answers
It is still helpful if you report a bug at bugzilla.proxmox.com
Hi
Would just like to know if this was fixed yet? Still on 3.4 but very scared to change due to this bug where you cannot deselect containers.
Would just like to know if this was fixed yet? Still on 3.4 but very scared to change due to this bug where you cannot deselect containers.
Didnt work for me, still cant choose anything but local for containers. In fact, I went back and made sure ONLY "Container" (not "Containers" as Proxmox support said here) was allowed in the list of types for the ZFS, and rebooted again, and still can't select it.
Last edited:
And i destroyed the ZFS cuz it was on /rpool/ROOT/pve-1, and put it on /rpool/ROOT, rebooted, still cant choose it. Forgot to remove "disk images" from the content to leave only "Container", so removed that, rebooted again, and STILL cant choose ZFS from the CT create dialog.Looking around further for possible issues, I also changed the "Nodes:" dialog selection for the ZFS storage area to the local node only, rebooted again, created again, STILL cant choose that pool.I had clicked on thin provision as well, so trying it without now... nope.One last combo to try, on pve-1 with storage Nodes: restricted to the node itself... nope.Is there some way to force this outside the GUI, on command line?
Last edited:
note this is all a stock install right out of the box, these are the first actions i've taken since install:- create CT as per normal under 3.4 etc - watch it fail- find out i need to create ZFS storage for it, try to install, cant choose anything but local, reboot- try again with all combos abovehere's my storage.cfgdir: local path /var/lib/vz maxfiles 0 content rootdir,vztmpl,images,isozfspool: data1 pool rpool content rootdirI suppose it's troubling that it says only 'rootdir' there.When I go to edit it, the dialog says "Container". Adding 'disk image' in the dialog back in for my zfspool storage gives me content rootdir,imagesremoving container and readding gives me content imagesre-adding container gives me content rootdir,imagesso is rootdir is synonymous with 'container'? Removed and readded and rebooted again, still cant choose the ZFS in the dialog.