| |||||||||||||
XFS: the filesystem of the future?XFS: the filesystem of the future?Posted Feb 5, 2012 19:45 UTC (Sun) by rilder (subscriber, #59804)In reply to: XFS: the filesystem of the future? by sbergman27 Parent article: XFS: the filesystem of the future?
If you need data integrity (like database commits) you will need to enforce it from application with fsync etc or have a SSD which provides such guarantees.
Speaking of write cache, the directive is to disable it on disk if you have another battery backed write cache sitting behind, or speaking of laptops you can have them since they are battery backed, no one says to disable cache completely.
You can start reading about it here -- http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_problem_w...
Speaking of caching in page cache, it is just to provide better I/O locality as mentioned in talk, it is flushed periodically, if it is flushed as and when required you will end up with seek nightmare with disk.
(Log in to post comments)
XFS: the filesystem of the future? Posted Feb 6, 2012 2:52 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]
> If you need data integrity (like database commits) you will need to enforce it from application with fsync etc or have a SSD which provides such guarantees.
having a SSD or battery backed cache does not replace doing fsyncs. If you don't do the fsync you don't know that the data is being written from the OS cache to the disk subsystem.
|
|||||||||||||