Search results

  1. H

    zvol volblocksize doubts

    Thanks for your answer wigor, But at least for the top filesystem block size. Does it makes sense to make it the same size as volblocksize when compression is enabled? If someone already knows would be cool to know it beforehand.
  2. H

    zvol volblocksize doubts

    Hello everybody, Right now I have a 4TB zvol that is attached to a VM that works as a fileserver over NFS/SAMBA. There are some issues with this zvol configuration (mainly related with volblocksize) and I would like to create a new one with the right config to replace the old one. This zvol is...
  3. H

    zvol using much more space than the imputable to parity + padding

    Thanks guys, didn't known that this was a thing. I was still in chapter 3, trying to understand the storage. I have done both and now results are different. Logicalused & logicalreferenced now meet the measure from inside the VM (2.4T) Referenced & usedbydataset show 3.54, that meets exactly...
  4. H

    zvol using much more space than the imputable to parity + padding

    Yes, I understand the concept. But what I'm trying to explain is that this do not explain all the gap between 2.4T and 5.46T. Or at least I think not. Sorry, didn't see your answer before posting mine. I'll think about it.
  5. H

    zvol using much more space than the imputable to parity + padding

    I have an hypothesis. The logical used space is 3.75T, that's 1.5x the space shown from inside the VM (2.4T), and 1.5x is expected to be the waste of my setup vs an ideal raidz1. If I done "maths" correctly in my first post. But if you look the definition for logical used it says that it...
  6. H

    zvol using much more space than the imputable to parity + padding

    Sorry fabian. I (believe I) understand what the doc wants to mean here but don't know how this solves my question. Probably my fault, but I have already done the maths for parity and padding waste in my original post and they don't match with the data. Have I done it wrong?
  7. H

    zvol using much more space than the imputable to parity + padding

    Hello everybody, I have a zvol with a volsize of 3.91T. This zvol is attached as a data disk to a VM that works as fileserver (SAMBA/NFS). Here you have the details of df -hT from inside the VM: 2.4T used from 3.9. The zvol has volblocksize = 8K, and is on a pool with only one RAIDz-1 of four...
  8. H

    Space available on Raidz2 on 4 disks

    I think that what Alwin tries to say is that you have 6.98Tb for all your data, where data is actual content, parity and padding. The actual real space that you will have available for your content will vary (decrease) depending on the ashift/sector size of your disks and the recordsize of the...
  9. H

    Understanding the disk layout automatically created by Proxmox VE installer

    Hello Aaron, Thanks for your answer. I think I have writted my questions too early. A lot of them were about ZFS fs and it was my first time with it. I have spent some days reading ZFS documentation and some of the questions have been resolved, some still stay and new ones have been created...
  10. H

    Understanding the disk layout automatically created by Proxmox VE installer

    Hello everybody, I have "inherited" a simple proxmox cluster with only one cluster, and I'm doing my best to catch up, reading the wiki, doc and forum threads. But there is something I still can't understand, that is the ZFS and proxmox storages layout. In the system there are two 1TB SSD and...