Jeremy Teo wrote:
Heya Anton,
On 10/17/06, Anton B. Rang <[EMAIL PROTECTED]> wrote:
No, the reason to try to match recordsize to the write size is so that
a small write does not turn into a large read + a large write. In
configurations where the disk is kept busy, multiplying 8K of data
transfer up to 256K hurts.
(Actually ZFS goes up to 128k not 256k (yet!))
Ah. I knew i was missing something. What COW giveth, COW taketh away...
Yes, although actually most non-COW filesystems have this same problem,
because they don't write partial blocks either, even though technically
they could. (And FYI, checksumming would "take away" the ability to
write partial blocks too.)
1) Set recordsize manually
2) Allow the blocksize of a file be changed even if there are multiple
blocks in the file.
Or, as has been suggested, add an API for apps to tell us the recordsize
before they populate the file.
--matt
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
