PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Linux)
Contents Index PreviousNext

Chapter 1 File System Functions> 1.3 High Availability

1.3.2 High-speed file system recovery

In case of a nodeTerm failure, fsck (8) must be executed for an ordinary file system to recover consistency. In most file systems, it is necessary to inspect all of the meta-dataTerm for the systems in order to recover consistency. If a node failure occurs, considerable time may be required before the file system actually becomes available.

The GFS Shared File System records operations that have changed the file system structure in an area called updated log. These operations include file creation and deletion. Using the dataTerm in the update log areaTerm allows the file system to recover from a system failure in less than a minute.

When recovering from a system failure, the GFS Shared File System retrieves the update logTerm in the recovery process. The file system then decides whether to invalidate or complete the file system operation that was done, and reflects the result. The file system structure can then be mounted and used without fully checking it.

As mentioned in the previous section, the GFS Shared File System operating on multiple nodeTerms does not require execution of sfcfsck(8) because consistency recovery processing is performed automatically in case of a node failure.

The sfcfsck(8) full check mode is also provided. To recover the file system from a hardware failure on the disk, execution of sfcfsck(8) in the full check mode may be required.

Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004