-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
yaml --- r: 38579 b: refs/heads/master c: e473142 h: refs/heads/master i: 38577: ea2e287 38575: c072edf v: v3
- Loading branch information
David Teigland
authored and
Steven Whitehouse
committed
Jan 18, 2006
1 parent
e0f1192
commit 652b8a1
Showing
2 changed files
with
45 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
--- | ||
refs/heads/master: 2ff4782374dde5e3d76daf8a82eae396c0f76567 | ||
refs/heads/master: e47314207032cfd1157b8c377df162839b32ea6f |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
Global File System | ||
------------------ | ||
|
||
http://sources.redhat.com/cluster/ | ||
|
||
GFS is a cluster file system. It allows a cluster of computers to | ||
simultaneously use a block device that is shared between them (with FC, | ||
iSCSI, NBD, etc). GFS reads and writes to the block device like a local | ||
file system, but also uses a lock module to allow the computers coordinate | ||
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 | ||
on one machine show up immediately on all other machines in the cluster. | ||
|
||
GFS uses interchangable inter-node locking mechanisms. Different lock | ||
modules can plug into GFS and each file system selects the appropriate | ||
lock module at mount time. Lock modules include: | ||
|
||
lock_nolock -- allows gfs to be used as a local file system | ||
|
||
lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking | ||
The dlm is found at linux/fs/dlm/ | ||
|
||
In addition to interfacing with an external locking manager, a gfs lock | ||
module is responsible for interacting with external cluster management | ||
systems. Lock_dlm depends on user space cluster management systems found | ||
at the URL above. | ||
|
||
To use gfs as a local file system, no external clustering systems are | ||
needed, simply: | ||
|
||
$ gfs2_mkfs -p lock_nolock -j 1 /dev/block_device | ||
$ mount -t gfs2 /dev/block_device /dir | ||
|
||
GFS2 is not on-disk compatible with previous versions of GFS. | ||
|
||
The following man pages can be found at the URL above: | ||
gfs2_mkfs to make a filesystem | ||
gfs2_fsck to repair a filesystem | ||
gfs2_grow to expand a filesystem online | ||
gfs2_jadd to add journals to a filesystem online | ||
gfs2_tool to manipulate, examine and tune a filesystem | ||
gfs2_quota to examine and change quota values in a filesystem | ||
mount.gfs2 to find mount options | ||
|