>>>>> "rt" == Robert Thurlow <[EMAIL PROTECTED]> writes:
rt> introduces a separate protection domain for the NFS link.
There are checksums in the ethernet FCS, checksums in IP headers,
checksums in UDP headers (which are sometimes ignored), and checksums
in TCP (which are not ignored). There might be an RPC layer checksum,
too, not sure.
Different arguments can be made against each, I suppose, but did you
have a particular argument in mind?
Have you experienced corruption with NFS that you can blame on the
network, not the CPU/memory/busses of the server and client?
I've experienced enough to make me buy stories of corruption in disks,
disk interfaces, and memory. but not yet with TCP so I'd like to hear
the story as well as the hypothetical argument, if there is one.
pgpE7CaaWOORQ.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
