Recent content by adowson

Managed to expand it to about 950GB, there's about 350GB left now. I had heard of the volblocksize attribute but mistakenly thought it only really influenced performance. It makes sense though since I'm guessing there's extra padding for the zvol. I think I might go back to the drawing board on...

Zpool. From the Proxmox GUI (Datacentre -> zpool) Output of the commands requested: root@pve:~# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zpool 29T 13.5T 15.5T - - 2% 46% 1.00x ONLINE - root@pve:~# zpool...

Realised why I was getting confused. I was looking for a UUID to mount it, but those are only generated for partitions, so partitionless disks only show /dev/sdb1. However, I'm running into a different problem now. I'm trying to expand the ZFS volume for the VM by 5837GiB. There is 10025GiB...

Huh, that's exactly what I did but I was under the impression that once you formatted it as GPT it wolud provide a /dev/sdb1 to put the ext4 on. I'll give gparted a try, think I'm having a layer 8 fault :).

I've only touched it on the VM end, just wasn't sure if I was doing something wrong. What I'm trying to do is use the ZFS-backed volume as a secondary storage device (for data) in the VM that I'll probably mount to /mnt. The VM itself is already installed on the primary SSD.

I managed to figure that out, sorry forgot to update. However, within Proxmox there is now /dev/zd0 which Proxmox has mapped to the Debian VM as /dev/sdb. How do I format the volume? Do I do it in the VM or in the Proxmox hypervisor? On the VM there is /dev/sdb but there's no /dev/sdb1 to...

I have a ZFS pool that has been migrated to Proxmox. I have a couple of VM's running that I all want to have access to my zpool. However, I want to manage folder permissions on the VM side since it's much easier to control access on a per-user basis. Can I create a logical block volume with...