gfs2_jadd(8) [debian man page]

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

NAME

       gfs2_jadd - Add journals to a GFS2 filesystem

SYNOPSIS

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

DESCRIPTION

       gfs2_jadd  is  used  to	add  journals (and a few other per-node files) to a GFS2 filesystem.  When this operation is complete, the journal
       index is updated so that machines mounting the filesystem at a later date will see the newly created journals in addition to  the  journals
       already there. Machines which are already running in the cluster are unaffected.

       You  may  only run gfs2_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported.  You only need to run
       gfs2_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.

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

OPTIONS

       -c MegaBytes
	      Initial size of each journal's quota change file

       -D     Print out debugging information about the filesystem layout.

       -h     Prints out a short usage message and exits.

       -J size
	      The size of the new journals in megabytes. The defaults to 32MB (the minimum size allowed is 8MB). If you want to  add  journals	of
	      different sizes to the filesystem, you'll need to run gfs2_jadd once for each different size of journal.

       -j num The number of new journals to add.

       -q     Be quiet.  Don't print anything.

       -u MegaBytes
	      Initial size of each journal's unlinked tag file

       -V     Version. Print version information, then exit.

SEE ALSO

       mkfs.gfs2(8) gfs2_grow(8)

																      gfs2_jadd(8)

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)