M
[email protected]
- Jan 1, 1970
- 0
Maybe enabling the write cache is not such a great idea after all...
Windows:
http://support.microsoft.com/?kbid=259716
"By enabling write caching, file system corruption and/or data loss
could occur if the machine experiences a power, device or system
failure and cannot be shutdown properly."
Linux:
http://sr5tech.com/write_back_cache_experiments.htm
"Write back cache on disks or controllers generated file system errors
that rendered the file systems either corrupted or inconsistent. Many
times, the file systems can no longer be mounted. We find that the
problems appear faster (typically fewer than 10 power cycles) when
cache is bigger, such as when there is also write-back cache on the
RAID controllers. Typically, we observed problems within 50 power
cycles."
http://www.jasonbrome.com/blog/archives/2004/04/03/writecache_enabled.html
(to disable write cache)
Thoughts, anyone?
Personally I'd rather have a slower, more reliable drive than have a
fast drive that needs frequent data restores...
Michael
Windows:
http://support.microsoft.com/?kbid=259716
"By enabling write caching, file system corruption and/or data loss
could occur if the machine experiences a power, device or system
failure and cannot be shutdown properly."
Linux:
http://sr5tech.com/write_back_cache_experiments.htm
"Write back cache on disks or controllers generated file system errors
that rendered the file systems either corrupted or inconsistent. Many
times, the file systems can no longer be mounted. We find that the
problems appear faster (typically fewer than 10 power cycles) when
cache is bigger, such as when there is also write-back cache on the
RAID controllers. Typically, we observed problems within 50 power
cycles."
http://www.jasonbrome.com/blog/archives/2004/04/03/writecache_enabled.html
(to disable write cache)
Thoughts, anyone?
Personally I'd rather have a slower, more reliable drive than have a
fast drive that needs frequent data restores...
Michael