On Mon, 2006-11-27 at 06:11 -0800, Marlanne DeLaSource wrote:
> What is even stranger is that if I copy a file in a raidz configuration
> (let's say /usr/bin/ls), we have different results out of regular commands :
>
> ls -l /usr/bin/ls /mapool/ls => same size
> ls -s /usr/bin/ls /mapool/ls => Different sizes
> du -s /usr/bin/ls /mapool/ls = > different sizes
>
> Shouldn't be those values similar ?
No, and you can even see different numbers between different UFS
partitions under certain circumstances.
ls -l shows the logical length in bytes of the file.
ls -s and du count the number of 512-byte disk blocks occupied by the
file; the on-disk footprint is an implementation artifact of the
filesystem.
On UFS, this number has always included the indirect blocks and excluded
file holes (ranges of zeros not backed by allocated blocks); moreover,
depending on the file system block size you use at newfs time, ls -s and
du can show different values when the same file is copied between
filesystems with different block sizes.
Given that ZFS already does other things quite differently it shouldn't
be that surprising that files occupy a different on-disk footprint...
- Bill
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
