head 1.4; access; symbols RPM_4_2_1:1.1.1.1 RPM_4_2:1.1.1.1 RPM_4_1_1:1.1.1.1 RPM_4_0_5:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.4 date 2008.01.02.09.55.22; author rse; state dead; branches; next 1.3; commitid z4cpSiAhOCXk5PLs; 1.3 date 2003.08.24.12.43.15; author rse; state Exp; branches; next 1.2; 1.2 date 2003.08.24.12.33.51; author rse; state dead; branches; next 1.1; 1.1 date 2002.08.14.16.32.05; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.08.14.16.32.05; author rse; state Exp; branches; next ; desc @@ 1.4 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB Reference Guide: Disk drive caches

Berkeley DB Reference Guide:
Programmer Notes

 PrevRefNext

Disk drive caches

Many disk drives contain onboard caches. Some of these drives include battery-backup or other functionality that guarantees that all cached data will be completely written if the power fails. These drives can offer substantial performance improvements over drives without caching support. However, some caching drives rely on capacitors or other mechanisms that guarantee only that the write of the current sector will complete. These drives can endanger your database and potentially cause corruption of your data.

To avoid losing your data, make sure the caching on your disk drives is properly configured so the drive will never report that data has been written unless the data is guaranteed to be written in the face of a power failure. Many times, this means that write-caching on the disk drive must be disabled.

PrevRefNext

Copyright Sleepycat Software @ 1.3 log @Resolve: RPM 4.1 -> RPM 4.1.1 @ text @@ 1.2 log @Resolve: RPM 4.0.5 -> RPM 4.1 @ text @@ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.5 @ text @@