GFS2: Update docs

Update a few things which were out of date, and fix a typo.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
This commit is contained in:
Steven Whitehouse 2009-05-19 10:23:23 +01:00
parent fe64d517df
commit e9ccb73ab5
2 changed files with 12 additions and 9 deletions

View file

@ -60,7 +60,7 @@ go_lock | Called for the first local holder of a lock
go_unlock | Called on the final local unlock of a lock go_unlock | Called on the final local unlock of a lock
go_dump | Called to print content of object for debugfs file, or on go_dump | Called to print content of object for debugfs file, or on
| error to dump glock to the log. | error to dump glock to the log.
go_type; | The type of the glock, LM_TYPE_..... go_type | The type of the glock, LM_TYPE_.....
go_min_hold_time | The minimum hold time go_min_hold_time | The minimum hold time
The minimum hold time for each lock is the time after a remote lock The minimum hold time for each lock is the time after a remote lock

View file

@ -11,18 +11,15 @@ their I/O so file system consistency is maintained. One of the nifty
features of GFS is perfect consistency -- changes made to the file system features of GFS is perfect consistency -- changes made to the file system
on one machine show up immediately on all other machines in the cluster. on one machine show up immediately on all other machines in the cluster.
GFS uses interchangable inter-node locking mechanisms. Different lock GFS uses interchangable inter-node locking mechanisms, the currently
modules can plug into GFS and each file system selects the appropriate supported mechanisms are:
lock module at mount time. Lock modules include:
lock_nolock -- allows gfs to be used as a local file system lock_nolock -- allows gfs to be used as a local file system
lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking
The dlm is found at linux/fs/dlm/ The dlm is found at linux/fs/dlm/
In addition to interfacing with an external locking manager, a gfs lock Lock_dlm depends on user space cluster management systems found
module is responsible for interacting with external cluster management
systems. Lock_dlm depends on user space cluster management systems found
at the URL above. at the URL above.
To use gfs as a local file system, no external clustering systems are To use gfs as a local file system, no external clustering systems are
@ -31,13 +28,19 @@ needed, simply:
$ mkfs -t gfs2 -p lock_nolock -j 1 /dev/block_device $ mkfs -t gfs2 -p lock_nolock -j 1 /dev/block_device
$ mount -t gfs2 /dev/block_device /dir $ mount -t gfs2 /dev/block_device /dir
GFS2 is not on-disk compatible with previous versions of GFS. If you are using Fedora, you need to install the gfs2-utils package
and, for lock_dlm, you will also need to install the cman package
and write a cluster.conf as per the documentation.
GFS2 is not on-disk compatible with previous versions of GFS, but it
is pretty close.
The following man pages can be found at the URL above: The following man pages can be found at the URL above:
gfs2_fsck to repair a filesystem fsck.gfs2 to repair a filesystem
gfs2_grow to expand a filesystem online gfs2_grow to expand a filesystem online
gfs2_jadd to add journals to a filesystem online gfs2_jadd to add journals to a filesystem online
gfs2_tool to manipulate, examine and tune a filesystem gfs2_tool to manipulate, examine and tune a filesystem
gfs2_quota to examine and change quota values in a filesystem gfs2_quota to examine and change quota values in a filesystem
gfs2_convert to convert a gfs filesystem to gfs2 in-place
mount.gfs2 to help mount(8) mount a filesystem mount.gfs2 to help mount(8) mount a filesystem
mkfs.gfs2 to make a filesystem mkfs.gfs2 to make a filesystem