Hi, the recordsize property is the maximum recored size used by zfs... the minimum will still be what is annoucent by the disk (512 bytes...). A zpool or zfs parameter for overriding the minimum block size would be the best option.
I've finished some tests with UFS with 8k block size and 4k frag size.. Perfs are very good (fitting the disks specs). newfs -v -b 8192 -f 4096 -o time -m 1 /dev/dsk/c5t7d0s0 I'm currently trying some zfs-over-ufs solutions ; perfs looks good (1/2 UFS perfs in throughput, 3/4 in iops). The next test will be creating volumes with 4k volblocksize property, and using them to build a zfs. I'll try the zfs_immediate_write_sz asap (but rebooting this fileserver is now difficult, since there is now production datas). Thanks for your help, best regards, Greg. -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
