Clarify assumption of filesystem metadata integrity.

Jeff Davis
pull/3/head
Simon Riggs 13 years ago
parent 8c3b87ca10
commit 1a091002cf
  1. 5
      doc/src/sgml/wal.sgml

@ -148,8 +148,9 @@
there is little it can do to make sure the data has arrived at a truly there is little it can do to make sure the data has arrived at a truly
non-volatile storage area. Rather, it is the non-volatile storage area. Rather, it is the
administrator's responsibility to make certain that all storage components administrator's responsibility to make certain that all storage components
ensure data integrity. Avoid disk controllers that have non-battery-backed ensure integrity for both data and filesystem metadata.
write caches. At the drive level, disable write-back caching if the Avoid disk controllers that have non-battery-backed write caches.
At the drive level, disable write-back caching if the
drive cannot guarantee the data will be written before shutdown. drive cannot guarantee the data will be written before shutdown.
If you use SSDs, be aware that many of these do not honor cache flush If you use SSDs, be aware that many of these do not honor cache flush
commands by default. commands by default.

Loading…
Cancel
Save