On 04/01/10 09:34, [email protected] wrote:
sync=disabled Synchronous requests are disabled. File system transactions only commit to stable storage on the next DMU transaction group commit which can be many seconds. This option will give the highest performance. However, it is very dangerous as ZFS would be ignoring the synchronous transaction demands of applications such as databases or NFS. Administrators should only use this when these risks are understood.Is there a partialy order defined for all filesystem operations?
File system operations will be written in order for all settings of the sync flag.
Specifically, will ZFS guarantee that when fsync()/O_DATA happens on a file,
(I assume by O_DATA you meant O_DSYNC).
that later transactions will not be in an earlier transaction group? (Or is this already the case?)
This is already the case.
Casper
_______________________________________________ opensolaris-arc mailing list [email protected]
