[PATCH 10/13] GFS: build and documentation
Add gfs to the build system and gfs2.txt to Documentation. Signed-off-by: Ken Preslan <[EMAIL PROTECTED]> Signed-off-by: David Teigland <[EMAIL PROTECTED]> --- Documentation/filesystems/gfs2.txt | 194 + fs/Kconfig | 15 ++ fs/Makefile|1 fs/gfs2/Makefile | 45 4 files changed, 255 insertions(+) --- a/fs/gfs2/Makefile 1970-01-01 07:30:00.0 +0730 +++ b/fs/gfs2/Makefile 2005-09-01 17:36:55.572076408 +0800 @@ -0,0 +1,45 @@ +obj-$(CONFIG_GFS2_FS) += gfs2.o +gfs2-y := \ + acl.o \ + bits.o \ + bmap.o \ + daemon.o \ + dir.o \ + eaops.o \ + eattr.o \ + glock.o \ + glops.o \ + inode.o \ + ioctl.o \ + jdata.o \ + lm.o \ + log.o \ + lops.o \ + lvb.o \ + main.o \ + meta_io.o \ + mount.o \ + ondisk.o \ + ops_address.o \ + ops_dentry.o \ + ops_export.o \ + ops_file.o \ + ops_fstype.o \ + ops_inode.o \ + ops_super.o \ + ops_vm.o \ + page.o \ + quota.o \ + resize.o \ + recovery.o \ + rgrp.o \ + super.o \ + sys.o \ + trans.o \ + unlinked.o \ + util.o + +obj-$(CONFIG_GFS2_FS) += locking/harness/ +obj-$(CONFIG_GFS2_FS) += locking/nolock/ +obj-$(CONFIG_GFS2_FS) += locking/dlm/ + --- a/fs/Makefile 2005-09-01 16:59:28.042752800 +0800 +++ b/fs/Makefile 2005-09-01 17:10:11.211976216 +0800 @@ -105,3 +105,4 @@ obj-$(CONFIG_OCFS2_FS) += ocfs2/ obj-$(CONFIG_RELAYFS_FS) += relayfs/ obj-$(CONFIG_9P_FS)+= 9p/ +obj-$(CONFIG_GFS2_FS) += gfs2/ --- a/fs/Kconfig2005-09-01 16:59:28.038753408 +0800 +++ b/fs/Kconfig2005-09-01 17:09:39.810749928 +0800 @@ -360,6 +360,21 @@ - POSIX ACLs - readpages / writepages (not user visible) +config GFS2_FS + tristate "GFS2 file system support" + depends on DLM + select FS_POSIX_ACL + help + A cluster filesystem. + + 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 filesystem, but also uses + a lock module to allow the computers coordinate their I/O so + filesystem consistency is maintained. One of the nifty features of + GFS is perfect consistency -- changes made to the filesystem on one + machine show up immediately on all other machines in the cluster. + config MINIX_FS tristate "Minix fs support" help --- a/Documentation/filesystems/gfs2.txt1970-01-01 07:30:00.0 +0730 +++ b/Documentation/filesystems/gfs2.txt2005-09-01 17:36:55.593073216 +0800 @@ -0,0 +1,194 @@ +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. GFS plugs into one +side of a module called "lock_harness" and different lock modules can plug +into the other side of the harness. Each gfs file system selects the +appropriate lock module at mount time. Lock modules include: + + lock_nolock -- does no real locking and 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/drivers/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 location 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 location above: + gfs2_mkfsto make a filesystem + gfs2_fsckto repair a filesystem + gfs2_growto expand a filesystem online + gfs2_jaddto add journals to a filesystem online + gfs2_toolto manipulate, examine and tune a filesystem + gfs2_quota to examine and change quota values in a filesystem + gfs2_mount to find mount options + +Mount options (from the gfs2_mount man page) + +
[PATCH 10/13] GFS: build and documentation
Add gfs to the build system and gfs2.txt to Documentation. Signed-off-by: Ken Preslan [EMAIL PROTECTED] Signed-off-by: David Teigland [EMAIL PROTECTED] --- Documentation/filesystems/gfs2.txt | 194 + fs/Kconfig | 15 ++ fs/Makefile|1 fs/gfs2/Makefile | 45 4 files changed, 255 insertions(+) --- a/fs/gfs2/Makefile 1970-01-01 07:30:00.0 +0730 +++ b/fs/gfs2/Makefile 2005-09-01 17:36:55.572076408 +0800 @@ -0,0 +1,45 @@ +obj-$(CONFIG_GFS2_FS) += gfs2.o +gfs2-y := \ + acl.o \ + bits.o \ + bmap.o \ + daemon.o \ + dir.o \ + eaops.o \ + eattr.o \ + glock.o \ + glops.o \ + inode.o \ + ioctl.o \ + jdata.o \ + lm.o \ + log.o \ + lops.o \ + lvb.o \ + main.o \ + meta_io.o \ + mount.o \ + ondisk.o \ + ops_address.o \ + ops_dentry.o \ + ops_export.o \ + ops_file.o \ + ops_fstype.o \ + ops_inode.o \ + ops_super.o \ + ops_vm.o \ + page.o \ + quota.o \ + resize.o \ + recovery.o \ + rgrp.o \ + super.o \ + sys.o \ + trans.o \ + unlinked.o \ + util.o + +obj-$(CONFIG_GFS2_FS) += locking/harness/ +obj-$(CONFIG_GFS2_FS) += locking/nolock/ +obj-$(CONFIG_GFS2_FS) += locking/dlm/ + --- a/fs/Makefile 2005-09-01 16:59:28.042752800 +0800 +++ b/fs/Makefile 2005-09-01 17:10:11.211976216 +0800 @@ -105,3 +105,4 @@ obj-$(CONFIG_OCFS2_FS) += ocfs2/ obj-$(CONFIG_RELAYFS_FS) += relayfs/ obj-$(CONFIG_9P_FS)+= 9p/ +obj-$(CONFIG_GFS2_FS) += gfs2/ --- a/fs/Kconfig2005-09-01 16:59:28.038753408 +0800 +++ b/fs/Kconfig2005-09-01 17:09:39.810749928 +0800 @@ -360,6 +360,21 @@ - POSIX ACLs - readpages / writepages (not user visible) +config GFS2_FS + tristate GFS2 file system support + depends on DLM + select FS_POSIX_ACL + help + A cluster filesystem. + + 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 filesystem, but also uses + a lock module to allow the computers coordinate their I/O so + filesystem consistency is maintained. One of the nifty features of + GFS is perfect consistency -- changes made to the filesystem on one + machine show up immediately on all other machines in the cluster. + config MINIX_FS tristate Minix fs support help --- a/Documentation/filesystems/gfs2.txt1970-01-01 07:30:00.0 +0730 +++ b/Documentation/filesystems/gfs2.txt2005-09-01 17:36:55.593073216 +0800 @@ -0,0 +1,194 @@ +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. GFS plugs into one +side of a module called lock_harness and different lock modules can plug +into the other side of the harness. Each gfs file system selects the +appropriate lock module at mount time. Lock modules include: + + lock_nolock -- does no real locking and 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/drivers/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 location 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 location above: + gfs2_mkfsto make a filesystem + gfs2_fsckto repair a filesystem + gfs2_growto expand a filesystem online + gfs2_jaddto add journals to a filesystem online + gfs2_toolto manipulate, examine and tune a filesystem + gfs2_quota to examine and change quota values in a filesystem + gfs2_mount to find mount options + +Mount options (from the gfs2_mount man page) + + lockproto=LockModuleName +