Differences between version 11 and previous revision of FileAllocationTable.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 11 | Last edited on Thursday, February 19, 2004 10:26:35 am | by PerryLorier | Revert |
| Older page: | version 10 | Last edited on Wednesday, February 11, 2004 1:28:20 pm | by AristotlePagaltzis | Revert |
@@ -65,7 +65,7 @@
# The MetaData tightly packed in a single block, which makes it an ideal candidate for caching.
# It is accessed very frequently, which keeps it in cache.
# It is often far away from the data itself, so serving it from the [Cache] saves ''huge'' amounts of HardDisk head movements.
-Beware though: running the [Cache] in WriteBack mode will further jeopardize the reliability of the already fragile [FAT]. Your best bet is to stick to
WriteThrough.
+Beware though: running the [Cache] in WriteBack mode will further jeopardize the reliability of the already fragile [FAT]. Your best bet is to stick with
WriteThrough.
Also, __never__ leave the disk [Cache] active while running system maintenance utilities such as a
