data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On macOS, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On OS X, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache On macOS, write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while

data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that will not survive a power failure. Many however, the method for doing this varies by operating system and drive type: • On Linux, IDE and SATA drives can be queried using hdparm -I; write caching is enabled if there is a * next to Write cache write caching can be prevented by setting wal_sync_method to fsync_writethrough. Recent SATA drives (those following ATAPI-6 or later) offer a drive cache flush command (FLUSH CACHE EXT), while