I must admit, I didn’t try it (yet) but what I read in a few minutes makes this a very nice feature for NethServer as a fileserver: VDO was originally developed by Permabit Technology Corp. as a proprietary set of kernel modules and userspace tools. This software and technology has been acquired by Red Hat, has been relicensed under the GPL (v2 or later), and this repository begins the process of preparing for integration with the upstream kernel.
VDO installs within the Linux device mapper framework, where it takes ownership of existing physical block devices and remaps these to new, higher-level block devices with data-efficiency capabilities. In other words: it adds deduplication to a basic RH/CentOS server.
It might be a (very) nice feature to add once NS 7.5 is available…
As far is i was able to understand from your link this is a quite huge slice between the system and the filesystem, and without a partition tool/management available from admin interface, is quite a “go/no-go” setup during the first install. Just like ZFS.
Which one is more reliable, scalable and solid? And also, easier to implement and manage?
tnx it is also in my “to see” list , these are the other links that I have marked
i must only find the time
but I do not think it can be included already in 7.5, but I think, however, we can see how it works and how to manage it with cockpit
If it is that simple, then maybe a little pointer in the wiki can be enough to add it.
Is it also functional from Nethserver-cockpit? Is the de-dup active?
Hello @Serhiy_Hryhoretskyy. Welcome to the NethServer community.
I have not heard before of anyone using VDO on NethServer Can you tell a bit more about your lab test? Besides the compression, what do we gain with VDO that is not available for ZFS (often used with proxmox) or even BTRFS (I think the default fs for Centos8)? This with the dedup in mind…
Here is presentation video by RH at DevConf, last january 2020. I think it clarifies quite well what VDO is and what it does.
