I am new to TrueNAS, and wanted to experiment with dedup on a small amount of storage, rather than the whole pool, as most of that data are not ideal candidates for dedup...
So I turned it on for a single zvol, which is configured as an iSCSI "Device" type extent, and connected to a Windows Hyper-V initiator. On the iSCSI disk, there lives then a virtual disk for my VM. This VM is a network DVR which stores H265 encoded video.
I was sort of figuring that since most of the background in the video is static, that data might be a good candidate for deduping. However, a couple days later, I checked using zpool list and zpool status, and am seeing the ratio at 1.00, and the LSIZE allocated and referenced both the same.
Does deduping really work in this scenario where I am using iSCSI block storage, and a virtual disk stored on that? Specifically I am asking if dedup can target the data inside a VHD - or is my issue more on the side of H265 video not really being dedupable, even if some of the video is static and shared between recordings?
So I turned it on for a single zvol, which is configured as an iSCSI "Device" type extent, and connected to a Windows Hyper-V initiator. On the iSCSI disk, there lives then a virtual disk for my VM. This VM is a network DVR which stores H265 encoded video.
I was sort of figuring that since most of the background in the video is static, that data might be a good candidate for deduping. However, a couple days later, I checked using zpool list and zpool status, and am seeing the ratio at 1.00, and the LSIZE allocated and referenced both the same.
Does deduping really work in this scenario where I am using iSCSI block storage, and a virtual disk stored on that? Specifically I am asking if dedup can target the data inside a VHD - or is my issue more on the side of H265 video not really being dedupable, even if some of the video is static and shared between recordings?