growfs(8) [freebsd man page]

GROWFS(8)						    BSD System Manager's Manual 						 GROWFS(8)

NAME

     growfs -- expand an existing UFS file system

SYNOPSIS

     growfs [-Ny] [-s size] special | filesystem

DESCRIPTION

     The growfs utility makes it possible to expand an UFS file system.  Before running growfs the partition or slice containing the file system
     must be extended using gpart(8).  If you are using volumes you must enlarge them by using gvinum(8).  The growfs utility extends the size of
     the file system on the specified special file.  The following options are available:

     -N      ``Test mode''.  Causes the new file system parameters to be printed out without actually enlarging the file system.

     -y      ``Expert mode''.  Usually growfs will ask you if you took a backup of your data before and will do some tests whether special is cur-
	     rently mounted or whether there are any active snapshots on the file system specified.  This will be suppressed.  So use this option
	     with great care!

     -s size
	     Determines the size of the file system after enlarging in sectors.  Size is the number of 512 byte sectors unless suffixed with a b,
	     k, m, g, or t which denotes byte, kilobyte, megabyte, gigabyte and terabyte respectively.	This value defaults to the size of the raw
	     partition specified in special (in other words, growfs will enlarge the file system to the size of the entire partition).

EXAMPLES

     Expand root file system to fill up available space:
	   growfs /

     Resize /dev/ada0p1 partition to 2GB and expand the file system:
	   gpart resize -i 1 -s 2G ada0
	   growfs -s 2G /dev/ada0p1

SEE ALSO

     dumpfs(8), ffsinfo(8), fsck(8), fsdb(8), gpart(8), newfs(8), tunefs(8)

HISTORY

     The growfs utility first appeared in FreeBSD 4.4.	The ability to resize mounted file systems was added in FreeBSD 10.0.

AUTHORS

     Christoph Herrmann <chm@FreeBSD.org>
     Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>
     The GROWFS team <growfs@Tomsoft.COM>
     Edward Tomasz Napierala <trasz@FreeBSD.org>

CAVEATS

     When expanding a file system mounted read-write, any writes to that file system will be temporarily suspended until the expansion is fin-
     ished.

BUGS

     Normally growfs writes cylinder group summary to disk and reads it again later for doing more updates.  This read operation will provide
     unexpected data when using -N.  Therefore, this part cannot really be simulated and will be skipped in test mode.

BSD
								 November 20, 2014							       BSD

GCONCAT(8)						    BSD System Manager's Manual 						GCONCAT(8)

NAME

     gconcat -- disk concatenation control utility

SYNOPSIS

     gconcat create [-v] name prov ...
     gconcat destroy [-fv] name ...
     gconcat label [-hv] name prov ...
     gconcat stop [-fv] name ...
     gconcat clear [-v] prov ...
     gconcat dump prov ...
     gconcat list
     gconcat status
     gconcat load
     gconcat unload

DESCRIPTION

     The gconcat utility is used for device concatenation configuration.  The concatenation can be configured using two different methods:
     ``manual'' or ``automatic''.  When using the ``manual'' method, no metadata are stored on the devices, so the concatenated device has to be
     configured by hand every time it is needed.  The ``automatic'' method uses on-disk metadata to detect devices.  Once devices are labeled,
     they will be automatically detected and configured.

     The first argument to gconcat indicates an action to be performed:

     create   Concatenate the given devices with specified name.  This is the ``manual'' method.  The kernel module geom_concat.ko will be loaded
	      if it is not loaded already.

     label    Concatenate the given devices with the specified name.  This is the ``automatic'' method, where metadata are stored in every
	      device's last sector.  The kernel module geom_concat.ko will be loaded if it is not loaded already.

     stop     Turn off existing concatenate device by its name.  This command does not touch on-disk metadata!

     destroy  Same as stop.

     clear    Clear metadata on the given devices.

     dump     Dump metadata stored on the given devices.

     list     See geom(8).

     status   See geom(8).

     load     See geom(8).

     unload   See geom(8).

     Additional options:

     -f      Force the removal of the specified concatenated device.

     -h      Hardcode providers' names in metadata.

     -v      Be more verbose.

SYSCTL VARIABLES

     The following sysctl(8) variables can be used to control the behavior of the CONCAT GEOM class.  The default value is shown next to each
     variable.

     kern.geom.concat.debug: 0
	     Debug level of the CONCAT GEOM class.  This can be set to a number between 0 and 3 inclusive.  If set to 0 minimal debug information
	     is printed, and if set to 3 the maximum amount of debug information is printed.

EXIT STATUS

     Exit status is 0 on success, and 1 if the command fails.

EXAMPLES

     The following example shows how to configure four disks for automatic concatenation, create a file system on it, and mount it:

	   gconcat label -v data /dev/da0 /dev/da1 /dev/da2 /dev/da3
	   newfs /dev/concat/data
	   mount /dev/concat/data /mnt
	   [...]
	   umount /mnt
	   gconcat stop data
	   gconcat unload

     Configure concatenated provider on one disk only.	Create file system.  Add two more disks and extend existing file system.

	   gconcat label data /dev/da0
	   newfs /dev/concat/data
	   gconcat label data /dev/da0 /dev/da1 /dev/da2
	   growfs /dev/concat/data

SEE ALSO

     geom(4), loader.conf(5), geom(8), growfs(8), gvinum(8), mount(8), newfs(8), sysctl(8), umount(8)

HISTORY

     The gconcat utility appeared in FreeBSD 5.3.

AUTHORS

     Pawel Jakub Dawidek <pjd@FreeBSD.org>

BSD
								   May 21, 2004 							       BSD