Most everyone knows about the async/sync issue in NFS. async lies to the client and says data has been written when it has not, and sync is dead slow but guarantees data integrity.
But how does this work in CIFS? I can find very little information about it. I did find reference to a configuration property for smb/server named "smbd/sync_enable" which can be accessed through svccfg and defaults to false. While I can't find reference to what it changes, I enabled it and my write speed dropped from 70 MB/s to 5.5 MB/s. I'm guessing it is similar to NFS sync. And is the asynchronous option for NFS (or the default behavior for CIFS) really an issue when the server has a UPS? Brendan Heading on a mailing list says: "Maybe the filesystem is full, maybe the disk is bad, maybe permissions have changed, etc." Reference: http://lists.us.dell.com/pipermail/linux-poweredge/2007-February/029724.html Are these really of concern? -- This message posted from opensolaris.org _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
