but if you do configuration and don't change it, all works properly. Under linux you should take care for ZFS because not all work as it should, specialy when you manage filesystem, make snapshot etc.
In real work this is replacement for RAM :) This can be very fast rotate disks or SSD disks. Of course, you can add to storage any cache disks. after this you can off deduplication and restore full performance. If you see any data should be deduplicated, you simply set deduplication on, rewrite some file to any temporary and finally replace. This is described in documentation.īut you can online set on/off deduplication on volume. This is, why writing files to ZFS volume mounted with FUSE, cause dramatically slow performance. Other way is time when data are deduplicated, this can be online (zfs) or offline (btrfs). This means, the same contents that repeats in the same file can be deduplicated. I don't understand, why linux doesn't support as drivers, it is way for many other operating systems / kernels.įile systems supports deduplication by 2 ways, deduplicate files, or blocks. Then you must patch kernel, and next install zfs tools for managament. If you want native support, look at the page. This is available as FUSE, but in this way it's very slow. Look at the page:, specialy at the table Features and column data deduplication. You can use BTRFS (very popular last time), OCFS or like this. Inode number is then saved, and original file content is destroyed (replaced) for all hardlinked names.īetter way is deduplication on filesystem layer. It is enough, any user put other file in the same name. You should prevent modification that file, because any user can damage file to other. This cause, all file names linked to the same inode, have the same access rights. Only file names are different because this is stored in directory structure, and other points to INODE properties. Notice, owner, group, mode, extended attributes, time and ACL (if you use this) is stored in INODE. If you'll do hardlinks, pay attention on rights on that file.
0 kommentar(er)
