- Joined
- Aug 19, 2017
- Messages
- 1,556
Okey, so usually my Dell T20 at home is a storage for home movies, pictures and documents.
For the past week i have been running
I'm doing this on my workstation running Ubuntu and I created a dataset for it with gzip compression and shared it with NFS from FreeNAS 11.2 - RC2. This works like a charm as the bottleneck is the broken disk being read and NFS otherwise easily saturates my 1GbE interface.
The space being used by the img files created by
Looking from Ubuntu over NFS the sizes reported are
TE95113NGHG1BS.img is in the process of being written, its about 60% done.
But looking in the FreeNAS ui, the dataset has only used a total of 234.58 GiB including the 63.84 GiB in "output" (the resulting tar archive I send over when Im done). The compression ratio reported by FreeNAS is 1.20x.
This is all reported the same by zfs
What is going on? There is over 540G written to the dataset so far, but only 235G "used" with a compression ratio of 1.20?
Does the long string of zeros from the img files not count against compression?
For the past week i have been running
ddrescue
trying to salvage data off a friends collection of crumbling disks.I'm doing this on my workstation running Ubuntu and I created a dataset for it with gzip compression and shared it with NFS from FreeNAS 11.2 - RC2. This works like a charm as the bottleneck is the broken disk being read and NFS otherwise easily saturates my 1GbE interface.
The space being used by the img files created by
ddrescue
is not making sens though.Looking from Ubuntu over NFS the sizes reported are
Code:
garm@ubuntu:~$ ls -alh /nfs/rescue/ total 171G drwxrwx--- 4 garm root 12 nov 19 21:24 . drwxr-xr-x 3 root root 4,0K nov 18 14:06 .. -rw-r--r-- 1 garm root 9,6G nov 19 11:06 05276483.img -rw-r--r-- 1 garm root 354 nov 19 08:27 05276483.map -rw-r--r-- 1 garm root 112G nov 18 17:29 071206DP1C10DJG95KVP.img -rw-r--r-- 1 garm root 382 nov 18 17:29 071206DP1C10DJG95KVP.map -rw-r--r-- 1 garm root 75G nov 19 05:04 3HV2YPF5.img -rw-r--r-- 1 garm root 356 nov 18 21:23 3HV2YPF5.map drwxr-xr-x 2 garm garm 4 nov 19 10:55 output -rw-r--r-- 1 garm root 278G nov 20 07:02 TE95113NGHG1BS.img -rw-r--r-- 1 garm root 45K nov 20 07:02 TE95113NGHG1BS.map
TE95113NGHG1BS.img is in the process of being written, its about 60% done.
But looking in the FreeNAS ui, the dataset has only used a total of 234.58 GiB including the 63.84 GiB in "output" (the resulting tar archive I send over when Im done). The compression ratio reported by FreeNAS is 1.20x.
This is all reported the same by zfs
Code:
[garm@nas ~]$ zfs list -o name,used,compressratio NAME USED RATIO babba/rescue 235G 1.20x babba/rescue/output 63.8G 1.00x
What is going on? There is over 540G written to the dataset so far, but only 235G "used" with a compression ratio of 1.20?
Does the long string of zeros from the img files not count against compression?