Installation guide

directory (and all its subdirectories). Existing files with zero length can also have data journaling

turned on or off.

Using the gfs_tool command, data journaling is enabled on a directory (and all its subdirector-

ies) or on a zero-length file by setting the inherit_jdata or jdata attribute flags to the directory

or file, respectively. The directory and file attribute flags can also be cleared.

Usage

Setting and Clearing the inherit_jdata Flag

gfs_tool setflag inherit_jdata Directory

gfs_tool clearflag inherit_jdata Directory

Setting and Clearing the jdata Flag

gfs_tool setflag jdata File

gfs_tool clearflag jdata File

Directory

Specifies the directory where the flag is set or cleared.

File

Specifies the zero-length file where the flag is set or cleared.

Examples

This example shows setting the inherit_jdata flag on a directory. All files created in the direct-

ory or any of its subdirectories will have the jdata flag assigned automatically. Any data written

to the files will be journaled.

gfs_tool setflag inherit_jdata /gfs1/data/

This example shows setting the jdata flag on a file. The file must be zero size. Any data written

to the file will be journaled.

gfs_tool setflag jdata /gfs1/datafile

9. Configuring atime Updates

Each file inode and directory inode has three time stamps associated with it:

• ctime — The last time the inode status was changed

• mtime — The last time the file (or directory) data was modified

• atime — The last time the file (or directory) data was accessed

If atime updates are enabled as they are by default on GFS and other Linux file systems then

Usage