gfs_grow(8) [debian man page]

gfs_grow(8)						      System Manager's Manual						       gfs_grow(8)

NAME

       gfs_grow - Expand a GFS filesystem

SYNOPSIS

       gfs_grow [OPTION]... <DEVICE|MOINTPOINT>...

DESCRIPTION

       gfs_grow is used to expand a GFS filesystem after the device upon which the filesystem resides has also been expanded.  By running gfs_grow
       on a GFS filesystem, you are requesting that any spare space between the current end of the filesystem and the end of the device is  filled
       with  a	newly  initialized GFS filesystem extension.  When this operation is complete, the resource index for the filesystem is updated so
       that all nodes in the cluster can use the extra storage space which has been added.

       You may only run gfs_grow on a mounted filesystem; expansion of unmounted filesystems is not supported.	You only need to run  gfs_grow	on
       one node in the cluster.  All the other nodes will see the expansion has occurred and automatically start to use the newly available space.

       You  must  be superuser to execute gfs_grow.  The gfs_grow tool tries to prevent you from corrupting your filesystem by checking as many of
       the likely problems as it can.  When expanding a filesystem, only the last step of  updating  the  resource  index  affects  the  currently
       mounted filesystem and so failure part way through the expansion process should leave your filesystem in its original unexpanded state.

       You  can run gfs_grow with the -Tv flags to get a display of the current state of a mounted GFS filesystem.  This can be useful to do after
       the expansion process to see if the changes have been successful.

       gfs_grow will consume all the remaining space in a device and add it to the filesystem.	If you want to add journals too, you need  to  add
       the journals first using gfs_jadd.

OPTIONS

       -h     Prints out a short usage message and exits.

       -q     Quiet. Turns down the verbosity level.

       -T     Test. Do all calculations, but do not write any data to the disk and do not expand the filesystem. This is used to discover what the
	      tool would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most  informa-
	      tion from this option.

       -V     Version. Print out version information, then exit.

       -v     Verbose. Turn up verbosity of messages.

SEE ALSO

       mkfs.gfs(8) gfs_jadd(8)

																       gfs_grow(8)

mkfs.gfs(8)						      System Manager's Manual						       mkfs.gfs(8)

NAME

       mkfs.gfs - Make a GFS filesystem

SYNOPSIS

       mkfs.gfs [OPTION]... DEVICE

DESCRIPTION

       mkfs.gfs is used to create a Global File System.

OPTIONS

       -b BlockSize
	      Set  the	filesystem  block  size  to  BlockSize (must be a power of two).  The minimum block size is 512.  The FS block size cannot
	      exceed the machine's memory page size.  On the most architectures (i386, x86_64, s390, s390x), the memory page size is  4096  bytes.
	      On other architectures it may be bigger.	The default block size is 4096 bytes.  In general, GFS filesystems should not deviate from
	      the default value.

       -D     Enable debugging output.

       -h     Print  out  a  help  message  describing	available options, then exit.

       -J MegaBytes
	      The size of the journals in Megabytes. The default journal size is 128 megabytes.  The minimum size is 32 megabytes.

       -j Number
	      The number of journals for mkfs.gfs to create.  You need at least one journal per machine that will mount the filesystem.

       -O     This option prevents mkfs.gfs from asking for confirmation before writing the filesystem.

       -p LockProtoName
	      LockProtoName is the name of the	locking  protocol to use.  The locking protocol should be lock_dlm for a clustered file system	or
	      if you are using GFS as a local filesystem (1 node only), you can specify the lock_nolock protocol.

       -q     Be quiet.  Don't print anything.

       -r MegaBytes
	      mkfs.gfs	will try to make Resource Groups (RGs) about this big.	Minimum RG size is 32 MB.  Maximum RG size is 2048 MB.	A large RG
	      size may increase performance on very large file systems.  If not specified, mkfs.gfs will choose the RG size based on the  size	of
	      the  file  system:  average  size file systems will have 256 MB RGs, and bigger file systems will have bigger RGs for better perfor-
	      mance.

       -s Blocks
	      Journal segment size in filesystem blocks.  This value must be at least two and not large enough to produce a segment  size  greater
	      than 4MB.

       -t LockTableName
	      The  lock  table field appropriate to the lock module you're using.  It is clustername:fsname.  Clustername must match that in clus-
	      ter.conf; only members of this cluster are permitted to use this file system.  Fsname is a unique file system name used  to  distin-
	      guish this GFS file system from others created (1 to 16 characters).  Lock_nolock doesn't use this field.

       -V     Print program version information, then exit.

EXAMPLE

       mkfs.gfs -t mycluster:mygfs -p lock_dlm -j 2 /dev/vg0/mygfs
	      This  will  make	a  Global  File System on the block device "/dev/vg0/mygfs".  It will belong to "mycluster" and register itself as
	      wanting locking for "mygfs".  It will use DLM for locking and make two journals.

																       mkfs.gfs(8)