Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #63
Difficulty: Easy
Blackberry was the first company to use the Emoji for mobile devices.
True or False?
Linux & Unix Commands - Search Man Pages

geom(8) [freebsd man page]

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

NAME
geom -- universal control utility for GEOM classes SYNOPSIS
geom class help geom class list [-a] [name ...] geom class status [-ags] [name ...] geom class load [-v] geom class unload [-v] DESCRIPTION
The geom utility is used to control various GEOM classes. A class has to be aware of geom(8) communication methods, but there are also some standard commands which can be used for existing geom(8) unaware classes. Here is the list of standard commands: help List all available commands for the given class. list Print detailed information (within the given class) about all geoms (if no additional arguments were specified) or the given geoms. This command is only available if the given class exists in the kernel. Additional options include: -a Print information for geoms without providers. status Print general information (within the given class) about all geoms (if no additional arguments were specified) or the given geoms. This command is only available if the given class exists in the kernel. Additional options include: -a When used with -g, print status for geoms without providers. -g Report statuses for geoms instead of providers. -s Produce script-friendly output. load Load the kernel module that implements the given class. This command is only available if the class does not yet exist in the kernel and the file geom_<class>.ko can be found in one of the directories specified in kern.module_path sysctl. unload Unload the kernel module which implements the given class. This command is only available if the given class is loaded as a kernel module. Class-specific commands are implemented as shared libraries which are stored in /lib/geom/ directory and are loaded via dlopen(3) function when the class name is known. When a class-specific shared library exists, a direct utility should also be available under the name of gclass. Currently available classes which are aware of geom(8): o CACHE o CONCAT o ELI o JOURNAL o LABEL o MIRROR o MOUNTVER o MULTIPATH o NOP o PART o RAID o RAID3 o SCHED o SHSEC o STRIPE o VIRSTOR ENVIRONMENT
The following environment variables affect the execution of geom: GEOM_LIBRARY_PATH Specifies the path where shared libraries are stored instead of /lib/geom/. Multiple paths can be specified with a colon- separated list of paths. EXIT STATUS
Exit status is 0 on success, and 1 if the command fails. EXAMPLES
The following example shows how to set up a stripe on three disks for automatic configuration: geom stripe label -v -s 65536 data /dev/da0 /dev/da1 /dev/da2 or: gstripe label -v -s 65536 data /dev/da0 /dev/da1 /dev/da2 Print the list of all providers from the DISK class: geom disk list Unload a kernel module which implements the MD class: geom md unload SEE ALSO
libgeom(3), geom(4), gcache(8), gconcat(8), geli(8), gjournal(8), glabel(8), gmirror(8), gmountver(8), gmultipath(8), gnop(8), gpart(8), graid3(8), gsched(8), gshsec(8), gstripe(8), gvirstor(8) HISTORY
The geom utility appeared in FreeBSD 5.3. AUTHORS
Pawel Jakub Dawidek <pjd@FreeBSD.org> BSD
January 5, 2011 BSD

Check Out this Related Man Page

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

NAME
gstripe -- control utility for striped devices SYNOPSIS
gstripe create [-v] [-s stripesize] name prov prov ... gstripe destroy [-fv] name ... gstripe label [-hv] [-s stripesize] name prov prov ... gstripe stop [-fv] name ... gstripe clear [-v] prov ... gstripe dump prov ... gstripe list gstripe status gstripe load gstripe unload DESCRIPTION
The gstripe utility is used for setting up a stripe on two or more disks. The striped device can be configured using two different methods: ``manual'' or ``automatic''. When using the ``manual'' method, no metadata are stored on the devices, so the striped device has to be con- figured 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 gstripe indicates an action to be performed: create Set up a striped device from the given devices with specified name. This is the ``manual'' method and the stripe will not exist after a reboot (see DESCRIPTION above). The kernel module geom_stripe.ko will be loaded if it is not loaded already. label Set up a striped device from 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_stripe.ko will be loaded if it is not loaded already. stop Turn off an existing striped 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 striped device. -h Hardcode providers' names in metadata. -s stripesize Specifies size of stripe block in bytes. The stripesize must be a multiple of the largest sector size of all the providers. -v Be more verbose. SYSCTL VARIABLES
The following sysctl(8) variables can be used to control the behavior of the STRIPE GEOM class. The default value is shown next to each variable. kern.geom.stripe.debug: 0 Debug level of the STRIPE 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. kern.geom.stripe.fast: 0 If set to a non-zero value enable ``fast mode'' instead of the normal ``economic mode''. Compared to ``economic mode'', ``fast mode'' uses more memory, but it is much faster for smaller stripe sizes. If enough memory cannot be allocated, STRIPE will fall back to ``economic mode''. kern.geom.stripe.maxmem: 13107200 Maximum amount of memory that can be consumed by ``fast mode'' (in bytes). This sysctl(8) variable is read-only and can only be set as a tunable in loader.conf(5). kern.geom.stripe.fast_failed A count of how many times ``fast mode'' has failed due to an insufficient amount of memory. If this value is large, you should con- sider increasing the kern.geom.stripe.maxmem value. EXIT STATUS
Exit status is 0 on success, and 1 if the command fails. EXAMPLES
The following example shows how to set up a striped device from four disks with a 128KB stripe size for automatic configuration, create a file system on it, and mount it: gstripe label -v -s 131072 data /dev/da0 /dev/da1 /dev/da2 /dev/da3 newfs /dev/stripe/data mount /dev/stripe/data /mnt [...] umount /mnt gstripe stop data gstripe unload COMPATIBILITY
The gstripe interleave is in number of bytes, unlike ccdconfig(8) which use the number of sectors. A ccdconfig(8) ileave of '128' is 64 KB (128 512B sectors). The same stripe interleave would be specified as '65536' for gstripe. SEE ALSO
geom(4), loader.conf(5), ccdconfig(8), geom(8), gvinum(8), mount(8), newfs(8), sysctl(8), umount(8) HISTORY
The gstripe utility appeared in FreeBSD 5.3. AUTHORS
Pawel Jakub Dawidek <pjd@FreeBSD.org> BSD
May 21, 2004 BSD

Featured Tech Videos