|LVRESIZE(8)||System Manager's Manual||LVRESIZE(8)|
[ option_args ]
[ position_args ]
--alloc contiguous|cling|cling_by_tags|normal| anywhere| inherit
--type linear|striped|snapshot|mirror|raid| thin| cache|thin-pool|cache-pool
-y|--yes lvextend(8) and lvreduce(8) for more information.
[ -l|--extents [+|-] Number[PERCENT] ][ -r|--resizefs ][ --poolmetadatasize [+]Size[m|UNIT] ][ COMMON_OPTIONS ]
[ PV ... ]-
[ -r|--resizefs ][ COMMON_OPTIONS ]
[ COMMON_OPTIONS ]
[ PV ... ]-
[ -A|--autobackup y|n ][ -f|--force ][ -n|--nofsck ][ -i|--stripes Number ][ -I|--stripesize Size[k|UNIT] ][ --alloc contiguous|cling|cling_by_tags|normal| anywhere| inherit ][ --nosync ][ --noudevsync ][ --reportformat basic|json ][ --type linear|striped|snapshot|mirror|raid| thin| cache|thin-pool|cache-pool ]
[ -d|--debug ][ -h|--help ][ -q|--quiet ][ -t|--test ][ -v|--verbose ][ -y|--yes ][ --commandprofile String ][ --config String ][ --driverloaded y|n ][ --longhelp ][ --profile String ][ --version ]
--alloc contiguous|cling|cling_by_tags|normal|anywhere|inheritDetermines the allocation policy when a command needs to allocate Physical Extents (PEs) from the VG. Each VG and LV has an allocation policy which can be changed with vgchange/lvchange, or overriden on the command line. normal applies common sense rules such as not placing parallel stripes on the same PV. inherit applies the VG policy to an LV. contiguous requires new PEs be placed adjacent to existing PEs. cling places new PEs on the same PV as existing PEs in the same stripe of the LV. If there are sufficient PEs for an allocation, but normal does not use them, anywhere will use them even if it reduces performance, e.g. by placing two stripes on the same PV. Optional positional PV args on the command line can also be used to limit which PVs the command will use for allocation. See lvm(8) for more information about allocation.
-A|--autobackup y|nSpecifies if metadata should be backed up automatically after a change. Enabling this is strongly advised! See vgcfgbackup(8) for more information.
--commandprofile StringThe command profile to use for command configuration. See lvm.conf(5) for more information about profiles.
--config StringConfig settings for the command. These override lvm.conf settings. The String arg uses the same format as lvm.conf, or may use section/field syntax. See lvm.conf(5) for more information about config.
-d|--debug ...Set debug level. Repeat from 1 to 6 times to increase the detail of messages sent to the log file and/or syslog (if configured).
--driverloaded y|nIf set to no, the command will not attempt to use device-mapper. For testing and debugging.
-l|--extents [ +|-]Number[PERCENT]Specifies the new size of the LV in logical extents. The --size and --extents options are alternate methods of specifying size. The total number of physical extents used will be greater when redundant data is needed for RAID levels. An alternate syntax allows the size to be determined indirectly as a percentage of the size of a related VG, LV, or set of PVs. The suffix %VG denotes the total size of the VG, the suffix %FREE the remaining free space in the VG, and the suffix %PVS the free space in the specified PVs. For a snapshot, the size can be expressed as a percentage of the total size of the origin LV with the suffix %ORIGIN (100%ORIGIN provides space for the whole origin). When expressed as a percentage, the size defines an upper limit for the number of logical extents in the new LV. The precise number of logical extents in the new LV is not determined until the command has completed. When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
-f|--force ...Override various checks, confirmations and protections. Use with extreme caution.
-h|--helpDisplay help text.
--longhelpDisplay long help text.
-n|--nofsckDo not perform fsck before resizing filesystem when filesystem requires it. You may need to use --force to proceed with this option.
--nosyncCauses the creation of mirror, raid1, raid4, raid5 and raid10 to skip the initial synchronization. In case of mirror, raid1 and raid10, any data written afterwards will be mirrored, but the original contents will not be copied. In case of raid4 and raid5, no parity blocks will be written, though any data written afterwards will cause parity blocks to be stored. This is useful for skipping a potentially long and resource intensive initial sync of an empty mirror/raid1/raid4/raid5 and raid10 LV. This option is not valid for raid6, because raid6 relies on proper parity (P and Q Syndromes) being created during initial synchronization in order to reconstruct proper user date in case of device failures. raid0 and raid0_meta do not provide any data copies or parity support and thus do not support initial synchronization.
--noudevsyncDisables udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. Only use this if udev is not running or has rules that ignore the devices LVM creates.
--poolmetadatasize [ +]Size[m|UNIT]Specifies the new size of the pool metadata LV. The plus prefix + can be used, in which case the value is added to the current size.
--profile StringAn alias for --commandprofile or --metadataprofile, depending on the command.
-q|--quiet ...Suppress output and log messages. Overrides --debug and --verbose. Repeat once to also suppress any prompts with answer 'no'.
--reportformat basic|jsonOverrides current output format for reports which is defined globally by the report/output_format setting in lvm.conf. basic is the original format with columns and rows. If there is more than one report per command, each report is prefixed with the report name for identification. json produces report output in JSON format. See lvmreport(7) for more information.
-r|--resizefsResize underlying filesystem together with the LV using fsadm(8).
-L|--size [ +|-]Size[m|UNIT]Specifies the new size of the LV. The --size and --extents options are alternate methods of specifying size. The total number of physical extents used will be greater when redundant data is needed for RAID levels. When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
-i|--stripes NumberSpecifies the number of stripes in a striped LV. This is the number of PVs (devices) that a striped LV is spread across. Data that appears sequential in the LV is spread across multiple devices in units of the stripe size (see --stripesize). This does not change existing allocated space, but only applies to space being allocated by the command. When creating a RAID 4/5/6 LV, this number does not include the extra devices that are required for parity. The largest number depends on the RAID type (raid0: 64, raid10: 32, raid4/5: 63, raid6: 62), and when unspecified, the default depends on the RAID type (raid0: 2, raid10: 2, raid4/5: 3, raid6: 5.) To stripe a new raid LV across all PVs by default, see lvm.conf allocation/raid_stripe_all_devices.
-I|--stripesize Size[k|UNIT]The amount of data that is written to one device before moving to the next in a striped LV.
-t|--testRun in test mode. Commands will not update metadata. This is implemented by disabling all metadata writing but nevertheless returning success to the calling function. This may lead to unusual error messages in multi-stage operations if a tool relies on reading back metadata it believes has changed but hasn't.
--type linear|striped|snapshot|mirror|raid|thin|cache|thin-pool|cache-poolThe LV type, also known as "segment type" or "segtype". See usage descriptions for the specific ways to use these types. For more information about redundancy and performance ( raid<N>, mirror, striped, linear) see lvmraid(7). For thin provisioning ( thin, thin-pool) see lvmthin(7). For performance caching ( cache, cache-pool) see lvmcache(7). For copy-on-write snapshots ( snapshot) see usage definitions. Several commands omit an explicit type option because the type is inferred from other options or shortcuts (e.g. --stripes, --mirrors, --snapshot, --virtualsize, --thin, --cache). Use inferred types with care because it can lead to unexpected results.
-v|--verbose ...Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr.
--versionDisplay version information.
-y|--yesDo not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)
LVLogical Volume name. See lvm(8) for valid names. An LV positional arg generally includes the VG name and LV name, e.g. VG/LV. LV followed by _<type> indicates that an LV of the given type is required. (raid represents raid<N> type)
PVPhysical Volume name, a device path under /dev. For commands managing physical extents, a PV positional arg generally accepts a suffix indicating a range (or multiple ranges) of physical extents (PEs). When the first PE is omitted, it defaults to the start of the device, and when the last PE is omitted it defaults to end. Start and end range (inclusive): PV[:PE-PE]... Start and length range (counting from 0): PV[:PE+PE]...
StringSee the option description for information about the string content.
Size[UNIT]Size is an input number that accepts an optional unit. Input units are always treated as base two values, regardless of capitalization, e.g. 'k' and 'K' both refer to 1024. The default input unit is specified by letter, followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE. b|B is bytes, s|S is sectors of 512 bytes, k|K is kilobytes, m|M is megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes, e|E is exabytes. (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)lvm(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter.
|LVM TOOLS 2.02.177(2) (2017-12-18)||Red Hat, Inc.|