ZFS. No error message when copying a 100 GiB file on a 22 GiB pool

[Maurizio Vairani]

Il 29/03/2017 14:21, Andriy Gapon ha scritto:
> On 29/03/2017 12:06, Maurizio Vairani wrote:
>> The PC is running:
>>
>> # uname -a
>>
>> FreeBSD clover-nas2 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22
>> 06:12:04 UTC 2017
>> root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>>
>> I need to copy a 100 GiB file, Win7.img, to another machine. The idea is to use
>> a fast USB 3 SSD. The pool on it, zdata, was created with the command:
>>
>> # zpool create -m /zdata -O compression=lz4 -O atime=off zdata
>> diskid/DISK-00000000000000000000
>>
>>
>> # zpool list zdata
>>
>> NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
>>
>> zdata  22.2G  4.85M  22.2G -16% 0%  1.00x  ONLINE  -
>>
>>
>> # du -hA Win7.img
>>
>> 100GWin7.img
>>
>> # du -h Win7.img
>>
>> 55GWin7.img
>>
>>
>> # /bin/cp Win7.img /zdata/
>>
>> No error message is printed. The file on zdata is truncated:
>>
>>
>> # du -Ah  /zdata/Win7.img
>>
>> 46G/zdata/Win7.img
>>
>> # du -h  /zdata/Win7.img
>>
>> 22G/zdata/Win7.img
> Does stat(1) also report a different size?
Yes
> Does md5 also report different content?
Yes

# stat Win7.img
901358515 463 -rw-r--r-- 1 root wheel 4294967295 107374182400 "Mar 24 
15:40:41 2017" "Mar 24 16:18:14 2017" "Mar 24 16:18:14 2017" "Mar 24 
15:40:41 2017" 131072 114638073 0x800 Win7.img
# md5 Win7.img
MD5 (Win7.img) = 92810cda676cd22cc726c17918bf3cee

# stat /zdata/Win7.img
3839449709 8 -rw-r--r-- 1 root wheel 4294967295 49498554368 "Mar 28 
16:29:41 2017" "Mar 28 16:36:24 2017" "Mar 28 16:36:24 2017" "Mar 28 
16:29:41 2017" 131072 45193337 0x800 /zdata/Win7.img
# md5 /zdata/Win7.img
MD5 (/zdata/Win7.img) = b7c3f59e0387ac810b4bbda6eade99db