A second kind of file system, such as FAT on Windows NT and most UNIX file systems, is called a lazy-write file system. This type was designed to speed up disk access. Assuming that disk crashes were not a regular occurrence, a lazy-write file system was designed to use an intelligent cache-management strategy and provide a way to recover data (such as the chkdsk utility) should something happen to the disk.
All data is accessed via the disk cache. While the user searches directories or reads files, data to be written to disk is allowed to accumulate in the cache. Thus, the user never has to wait while disk-writes are performed. Plus, the user is able to access all the file-system resources that might otherwise be allocated for disk writing. Data gets written to disk when the computer's resources are in low demand, rather than in serial fashion.
If the same data is modified several times, all those modifications are captured in the disk cache. The result is that the file system needs to write to disk only once to update the data. That is, the file system opens the file once and then performs all of the updates together before closing the file.
The disadvantage of a lazy-write file system is that, in the event of a disk crash, recovery could take much longer than with a careful-write file system. This is because a utility such as chkdsk must then scan the entire volume to recover, checking what should have been written to disk against what actually was written.