On 11-Mar-07, at 11:22 PM, Stuart Low wrote:
Heya,
I believe Robert and Darren have offered sufficient explanations: You
cannot be assured of committed data unless you've sync'd it. You are
only risking data loss if your users and/or applications assume data
is committed without seeing a completed sync, which would be a design
error. This applies to any filesystem.
Which, from memory with NFS would be the 'sync' exports option.
Or at application discretion with fsync()/fdatasync()? (end of
transaction). While I'm not an NFS guru, I'm pretty sure this has
been previously discussed on this list. If I understand the OP's post
correctly, his issue is not about ZFS but more not realising he
actually needs commit semantics (as Robert quickly pointed out) -
coupled with not realising that ALL filesystems will probably lose
uncommitted data if you yank the cable.
--Toby
Just my 2c,
Stuart
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
