On Fri, May 16, 2008 at 11:03:15PM +0100, Jamie Lokier wrote: > The MacOS X folks decided that speed is most important for fsync(). > fsync() does not guarantee commit to platter. *But* they added an > fcntl() for applications to request a commit to platter, which SQLite > at least uses. I don't know if MacOS X uses barriers for filesystem > operations. Out of curiosity, exactly *what* semantics did MacOS X give fsync(), then? Did it simply start the process of staging writes to disk, but not wait for the writes to hit the platter before returning? That's basically the equivalent of ext3's barrier=0. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
