{ "content": [ { "type": "text", "text": "# lvcreate (man)\n\n## NAME\n\nlvcreate — Create a logical volume\n\n## SYNOPSIS\n\nlvcreate optionargs positionargs\n[ optionargs ]\n[ positionargs ]\n-a|--activate y|n|ay\n--addtag Tag\n--alloc contiguous|cling|clingbytags|normal|anywhere|inherit\n-A|--autobackup y|n\n-H|--cache\n--cachedevice PV\n--cachemetadataformat auto|1|2\n--cachemode writethrough|writeback|passthrough\n--cachepolicy String\n--cachepool LV\n--cachesettings String\n--cachesize Size[m|UNIT]\n--cachevol LV\n-c|--chunksize Size[k|UNIT]\n--commandprofile String\n--compression y|n\n--config String\n-C|--contiguous y|n\n-d|--debug\n--deduplication y|n\n--devices PV\n--devicesfile String\n--discards passdown|nopassdown|ignore\n--driverloaded y|n\n--errorwhenfull y|n\n-l|--extents Number[PERCENT]\n-h|--help\n-K|--ignoreactivationskip\n--ignoremonitoring\n--journal String\n--lockopt String\n--longhelp\n-j|--major Number\n--[raid]maxrecoveryrate Size[k|UNIT]\n--metadataprofile String\n--minor Number\n--[raid]minrecoveryrate Size[k|UNIT]\n--mirrorlog core|disk\n-m|--mirrors Number\n--monitor y|n\n-n|--name String\n--nohints\n--nolocking\n--nosync\n--noudevsync\n-p|--permission rw|r\n-M|--persistent y|n\n--poolmetadatasize Size[m|UNIT]\n--poolmetadataspare y|n\n--profile String\n-q|--quiet\n--raidintegrity y|n\n--raidintegrityblocksize Number\n--raidintegritymode String\n-r|--readahead auto|none|Number\n-R|--regionsize Size[m|UNIT]\n--reportformat basic|json\n-k|--setactivationskip y|n\n--setautoactivation y|n\n-L|--size Size[m|UNIT]\n-s|--snapshot\n-i|--stripes Number\n-I|--stripesize Size[k|UNIT]\n-t|--test\n-T|--thin\n--thinpool LV\n--type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo|vdo-pool|cache|cache-pool|\n\n## DESCRIPTION\n\nlvcreate creates a new LV in a VG. For standard LVs, this requires allocating logical extents\nfrom the VG's free physical extents. If there is not enough free space, the VG can be extend‐\ned with other PVs (vgextend(8)), or existing LVs can be reduced or removed (lvremove(8),\nlvreduce(8)).\n\n## TLDR\n\n> Create a logical volume in an existing volume group. A volume group is a collection of logical and physical volumes.\n\n- Create a logical volume of 10 gigabytes in the volume group `vg1`:\n `sudo lvcreate {{-L|--size}} 10G vg1`\n- Create a 1500 megabyte linear logical volume named `mylv` in the volume group `vg1`:\n `sudo lvcreate {{-L|--size}} 1500 {{-n|--name}} mylv vg1`\n- Create a logical volume called `mylv` that uses 60% of the total space in volume group `vg1`:\n `sudo lvcreate {{-l|--extents}} 60%VG {{-n|--name}} mylv vg1`\n- Create a logical volume called `mylv` that uses all the unallocated space in the volume group `vg1`:\n `sudo lvcreate {{-l|--extents}} 100%FREE {{-n|--name}} mylv vg1`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS** (1 subsections)\n- **DESCRIPTION** (1 subsections)\n- **USAGE**\n- **OPTIONS** (37 subsections)\n- **VARIABLES**\n- **ENVIRONMENT VARIABLES**\n- **ADVANCED USAGE**\n- **EXAMPLES** (18 subsections)\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "lvcreate", "section": "", "mode": "man", "summary": "lvcreate — Create a logical volume", "synopsis": "lvcreate optionargs positionargs\n[ optionargs ]\n[ positionargs ]\n-a|--activate y|n|ay\n--addtag Tag\n--alloc contiguous|cling|clingbytags|normal|anywhere|inherit\n-A|--autobackup y|n\n-H|--cache\n--cachedevice PV\n--cachemetadataformat auto|1|2\n--cachemode writethrough|writeback|passthrough\n--cachepolicy String\n--cachepool LV\n--cachesettings String\n--cachesize Size[m|UNIT]\n--cachevol LV\n-c|--chunksize Size[k|UNIT]\n--commandprofile String\n--compression y|n\n--config String\n-C|--contiguous y|n\n-d|--debug\n--deduplication y|n\n--devices PV\n--devicesfile String\n--discards passdown|nopassdown|ignore\n--driverloaded y|n\n--errorwhenfull y|n\n-l|--extents Number[PERCENT]\n-h|--help\n-K|--ignoreactivationskip\n--ignoremonitoring\n--journal String\n--lockopt String\n--longhelp\n-j|--major Number\n--[raid]maxrecoveryrate Size[k|UNIT]\n--metadataprofile String\n--minor Number\n--[raid]minrecoveryrate Size[k|UNIT]\n--mirrorlog core|disk\n-m|--mirrors Number\n--monitor y|n\n-n|--name String\n--nohints\n--nolocking\n--nosync\n--noudevsync\n-p|--permission rw|r\n-M|--persistent y|n\n--poolmetadatasize Size[m|UNIT]\n--poolmetadataspare y|n\n--profile String\n-q|--quiet\n--raidintegrity y|n\n--raidintegrityblocksize Number\n--raidintegritymode String\n-r|--readahead auto|none|Number\n-R|--regionsize Size[m|UNIT]\n--reportformat basic|json\n-k|--setactivationskip y|n\n--setautoactivation y|n\n-L|--size Size[m|UNIT]\n-s|--snapshot\n-i|--stripes Number\n-I|--stripesize Size[k|UNIT]\n-t|--test\n-T|--thin\n--thinpool LV\n--type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo|vdo-pool|cache|cache-pool|", "tldr_summary": "Create a logical volume in an existing volume group. A volume group is a collection of logical and physical volumes.", "tldr_examples": [ { "description": "Create a logical volume of 10 gigabytes in the volume group `vg1`", "command": "sudo lvcreate {{-L|--size}} 10G vg1" }, { "description": "Create a 1500 megabyte linear logical volume named `mylv` in the volume group `vg1`", "command": "sudo lvcreate {{-L|--size}} 1500 {{-n|--name}} mylv vg1" }, { "description": "Create a logical volume called `mylv` that uses 60% of the total space in volume group `vg1`", "command": "sudo lvcreate {{-l|--extents}} 60%VG {{-n|--name}} mylv vg1" }, { "description": "Create a logical volume called `mylv` that uses all the unallocated space in the volume group `vg1`", "command": "sudo lvcreate {{-l|--extents}} 100%FREE {{-n|--name}} mylv vg1" } ], "tldr_source": "official", "flags": [ { "flag": "-a", "long": "--activate", "arg": null, "description": "Controls the active state of the new LV. y makes the LV active, or available. New LVs are made active by default. n makes the LV inactive, or unavailable, only when possible. In some cases, creating an LV requires it to be active. For example, COW snapshots of an active origin LV can only be created in the active state (this does not apply to thin snapshots). The --zero option normally requires the LV to be ac‐ tive. If autoactivation ay is used, the LV is only activated if it matches an item in lvm.conf(5) activation/autoactivationvolumelist. ay implies --zero n and --wipes‐ ignatures n. See lvmlockd(8) for more information about activation options for shared VGs. --addtag Tag Adds a tag to a PV, VG or LV. This option can be repeated to add multiple tags at once. See lvm(8) for information about tags. --alloc contiguous|cling|clingbytags|normal|anywhere|inherit Determines 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 overridden 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 allo‐ cation." }, { "flag": "-A", "long": "--autobackup", "arg": null, "description": "Specifies if metadata should be backed up automatically after a change. Enabling this is strongly advised! See vgcfgbackup(8) for more information." }, { "flag": "-H", "long": "--cache", "arg": null, "description": "Specifies the command is handling a cache LV or cache pool. See --type cache and --type cache-pool. See lvmcache(7) for more information about LVM caching. --cachedevice PV The name of a device to use for a cache. --cachemetadataformat auto|1|2 Specifies the cache metadata format used by cache target. --cachemode writethrough|writeback|passthrough Specifies when writes to a cache LV should be considered complete. writeback consid‐ ers a write complete as soon as it is stored in the cache pool. writethough considers a write complete only when it has been stored in both the cache pool and on the origin LV. While writethrough may be slower for writes, it is more resilient if something should happen to a device associated with the cache pool LV. With passthrough, all reads are served from the origin LV (all reads miss the cache) and all writes are for‐ warded to the origin LV; additionally, write hits cause cache block invalidates. See lvmcache(7) for more information. --cachepolicy String Specifies the cache policy for a cache LV. See lvmcache(7) for more information. --cachepool LV The name of a cache pool. --cachesettings String Specifies tunable kernel options for dm-cache or dm-writecache LVs. Use the form 'op‐ tion=value' or 'option1=value option2=value', or repeat --cachesettings for each op‐ tion being set. These settings override the default kernel behaviors which are usual‐ ly adequate. To remove cachesettings and revert to the default kernel behaviors, use --cachesettings 'default' for dm-cache or an empty string --cachesettings '' for dm- writecache. See lvmcache(7) for more information. --cachesize Size[m|UNIT] The size of cache to use. --cachevol LV The name of a cache volume." }, { "flag": "-c", "long": "--chunksize", "arg": null, "description": "The size of chunks in a snapshot, cache pool or thin pool. For snapshots, the value must be a power of 2 between 4KiB and 512KiB and the default value is 4. For a cache pool the value must be between 32KiB and 1GiB and the default value is 64. For a thin pool the value must be between 64KiB and 1GiB and the default value starts with 64 and scales up to fit the pool metadata size within 128MiB, if the pool metadata size is not specified. The value must be a multiple of 64KiB. See lvmthin(7) and lvmcache(7) for more information. --commandprofile String The command profile to use for command configuration. See lvm.conf(5) for more infor‐ mation about profiles. --compression y|n Controls whether compression is enabled or disable for VDO volume. See lvmvdo(7) for more information about VDO usage. --config String Config settings for the command. These override lvm.conf(5) settings. The String arg uses the same format as lvm.conf(5), or may use section/field syntax. See lvm.conf(5) for more information about config." }, { "flag": "-C", "long": "--contiguous", "arg": null, "description": "Sets or resets the contiguous allocation policy for LVs. Default is no contiguous al‐ location based on a next free principle. It is only possible to change a non-contigu‐ ous allocation policy to contiguous if all of the allocated physical extents in the LV are already contiguous." }, { "flag": "-d", "long": "--debug", "arg": null, "description": "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). --deduplication y|n Controls whether deduplication is enabled or disable for VDO volume. See lvmvdo(7) for more information about VDO usage. --devices PV Restricts the devices that are visible and accessible to the command. Devices not listed will appear to be missing. This option can be repeated, or accepts a comma sep‐ arated list of devices. This overrides the devices file. --devicesfile String A file listing devices that LVM should use. The file must exist in /etc/lvm/devices/ and is managed with the lvmdevices(8) command. This overrides the lvm.conf(5) de‐ vices/devicesfile and devices/usedevicesfile settings. --discards passdown|nopassdown|ignore Specifies how the device-mapper thin pool layer in the kernel should handle discards. ignore causes the thin pool to ignore discards. nopassdown causes the thin pool to process discards itself to allow reuse of unneeded extents in the thin pool. passdown causes the thin pool to process discards itself (like nopassdown) and pass the dis‐ cards to the underlying device. See lvmthin(7) for more information. --driverloaded y|n If set to no, the command will not attempt to use device-mapper. For testing and de‐ bugging. --errorwhenfull y|n Specifies thin pool behavior when data space is exhausted. When yes, device-mapper will immediately return an error when a thin pool is full and an I/O request requires space. When no, device-mapper will queue these I/O requests for a period of time to allow the thin pool to be extended. Errors are returned if no space is available af‐ ter the timeout. (Also see dm-thin-pool kernel module option nospacetimeout.) See lvmthin(7) for more information." }, { "flag": "-l", "long": "--extents", "arg": null, "description": "Specifies the size of the new 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 num‐ ber 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." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Display help text." }, { "flag": "-K", "long": "--ignoreactivationskip", "arg": null, "description": "Ignore the \"activation skip\" LV flag during activation to allow LVs with the flag set to be activated." }, { "flag": "", "long": "--ignoremonitoring", "arg": null, "description": "Do not interact with dmeventd unless --monitor is specified. Do not use this if dmeventd is already monitoring a device. --journal String Record information in the systemd journal. This information is in addition to infor‐ mation enabled by the lvm.conf log/journal setting. command: record information about the command. output: record the default command output. debug: record full command debugging. --lockopt String Used to pass options for special cases to lvmlockd. See lvmlockd(8) for more informa‐ tion." }, { "flag": "", "long": "--longhelp", "arg": null, "description": "Display long help text." }, { "flag": "-j", "long": "--major", "arg": null, "description": "Sets the major number of an LV block device. --[raid]maxrecoveryrate Size[k|UNIT] Sets the maximum recovery rate for a RAID LV. The rate value is an amount of data per second for each device in the array. Setting the rate to 0 means it will be unbound‐ ed. See lvmraid(7) for more information. --metadataprofile String The metadata profile to use for command configuration. See lvm.conf(5) for more in‐ formation about profiles. --minor Number Sets the minor number of an LV block device. --[raid]minrecoveryrate Size[k|UNIT] Sets the minimum recovery rate for a RAID LV. The rate value is an amount of data per second for each device in the array. Setting the rate to 0 means it will be unbound‐ ed. See lvmraid(7) for more information. --mirrorlog core|disk Specifies the type of mirror log for LVs with the \"mirror\" type (does not apply to the \"raid1\" type.) disk is a persistent log and requires a small amount of storage space, usually on a separate device from the data being mirrored. core is not persistent; the log is kept only in memory. In this case, the mirror must be synchronized (by copying LV data from the first device to others) each time the LV is activated, e.g. after reboot. mirrored is a persistent log that is itself mirrored, but should be avoided. Instead, use the raid1 type for log redundancy." }, { "flag": "-m", "long": "--mirrors", "arg": null, "description": "Specifies the number of mirror images in addition to the original LV image, e.g. --mirrors 1 means there are two images of the data, the original and one mirror image. Optional positional PV args on the command line can specify the devices the images should be placed on. There are two mirroring implementations: \"raid1\" and \"mirror\". These are the names of the corresponding LV types, or \"segment types\". Use the --type option to specify which to use (raid1 is default, and mirror is legacy) Use lvm.conf(5) global/mirrorsegtypedefault and global/raid10segtypedefault to config‐ ure the default types. See the --nosync option for avoiding initial image synchro‐ nization. See lvmraid(7) for more information. --monitor y|n Start (yes) or stop (no) monitoring an LV with dmeventd. dmeventd monitors kernel events for an LV, and performs automated maintenance for the LV in reponse to specific events. See dmeventd(8) for more information." }, { "flag": "-n", "long": "--name", "arg": null, "description": "Specifies the name of a new LV. When unspecified, a default name of \"lvol#\" is gener‐ ated, where # is a number generated by LVM." }, { "flag": "", "long": "--nohints", "arg": null, "description": "Do not use the hints file to locate devices for PVs. A command may read more devices to find PVs when hints are not used. The command will still perform standard hint file invalidation where appropriate." }, { "flag": "", "long": "--nolocking", "arg": null, "description": "Disable locking. Use with caution, concurrent commands may produce incorrect results." }, { "flag": "", "long": "--nosync", "arg": null, "description": "Causes the creation of mirror, raid1, raid4, raid5 and raid10 to skip the initial syn‐ chronization. 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 in‐ tensive 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) be‐ ing created during initial synchronization in order to reconstruct proper user date in case of device failures. raid0 and raid0meta do not provide any data copies or pari‐ ty support and thus do not support initial synchronization." }, { "flag": "", "long": "--noudevsync", "arg": null, "description": "Disables 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." }, { "flag": "-p", "long": "--permission", "arg": null, "description": "Set access permission to read only r or read and write rw." }, { "flag": "-M", "long": "--persistent", "arg": null, "description": "When yes, makes the specified minor number persistent. --poolmetadatasize Size[m|UNIT] Specifies the size of the new pool metadata LV. --poolmetadataspare y|n Enable or disable the automatic creation and management of a spare pool metadata LV in the VG. A spare metadata LV is reserved space that can be used when repairing a pool. --profile String An alias for --commandprofile or --metadataprofile, depending on the command." }, { "flag": "-q", "long": "--quiet", "arg": null, "description": "Suppress output and log messages. Overrides --debug and --verbose. Repeat once to al‐ so suppress any prompts with answer 'no'. --raidintegrity y|n Enable or disable data integrity checksums for raid images. --raidintegrityblocksize Number The block size to use for dm-integrity on raid images. The integrity block size should usually match the device logical block size, or the file system block size. It may be less than the file system block size, but not less than the device logical block size. Possible values: 512, 1024, 2048, 4096. --raidintegritymode String Use a journal (default) or bitmap for keeping integrity checksums consistent in case of a crash. The bitmap areas are recalculated after a crash, so corruption in those areas would not be detected. A journal does not have this problem. The journal mode doubles writes to storage, but can improve performance for scattered writes packed in‐ to a single journal write. bitmap mode can in theory achieve full write throughput of the device, but would not benefit from the potential scattered write optimization." }, { "flag": "-r", "long": "--readahead", "arg": null, "description": "Sets read ahead sector count of an LV. auto is the default which allows the kernel to choose a suitable value automatically. none is equivalent to zero." }, { "flag": "-R", "long": "--regionsize", "arg": null, "description": "Size of each raid or mirror synchronization region. lvm.conf(5) activation/raidre‐ gionsize can be used to configure a default. --reportformat basic|json Overrides current output format for reports which is defined globally by the re‐ port/outputformat setting in lvm.conf(5). 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." }, { "flag": "-k", "long": "--setactivationskip", "arg": null, "description": "Persistently sets (yes) or clears (no) the \"activation skip\" flag on an LV. An LV with this flag set is not activated unless the --ignoreactivationskip option is used by the activation command. This flag is set by default on new thin snapshot LVs. The flag is not applied to deactivation. The current value of the flag is indicated in the lvs lvattr bits. --setautoactivation y|n Set the autoactivation property on a VG or LV. Display the property with vgs or lvs \"-o autoactivation\". When the autoactivation property is disabled, the VG or LV will not be activated by a command doing autoactivation (vgchange, lvchange, or pvscan us‐ ing -aay.) If autoactivation is disabled on a VG, no LVs will be autoactivated in that VG, and the LV autoactivation property has no effect. If autoactivation is en‐ abled on a VG, autoactivation can be disabled for individual LVs." }, { "flag": "-L", "long": "--size", "arg": null, "description": "Specifies the size of the new 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." }, { "flag": "-s", "long": "--snapshot", "arg": null, "description": "Create a snapshot. Snapshots provide a \"frozen image\" of an origin LV. The snapshot LV can be used, e.g. for backups, while the origin LV continues to be used. This op‐ tion can create a COW (copy on write) snapshot, or a thin snapshot (in a thin pool.) Thin snapshots are created when the origin is a thin LV and the size option is NOT specified. Thin snapshots share the same blocks in the thin pool, and do not allocate new space from the VG. Thin snapshots are created with the \"activation skip\" flag, see --setactivationskip. A thin snapshot of a non-thin \"external origin\" LV is creat‐ ed when a thin pool is specified. Unprovisioned blocks in the thin snapshot LV are read from the external origin LV. The external origin LV must be read-only. See lvmthin(7) for more information about LVM thin provisioning. COW snapshots are creat‐ ed when a size is specified. The size is allocated from space in the VG, and is the amount of space that can be used for saving COW blocks as writes occur to the origin or snapshot. The size chosen should depend upon the amount of writes that are expect‐ ed; often 20% of the origin LV is enough. If COW space runs low, it can be extended with lvextend (shrinking is also allowed with lvreduce.) A small amount of the COW snapshot LV size is used to track COW block locations, so the full size is not avail‐ able for COW data blocks. Use lvs to check how much space is used, and see --monitor to to automatically extend the size to avoid running out of space." }, { "flag": "-i", "long": "--stripes", "arg": null, "description": "Specifies 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 com‐ mand. 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(5) allocation/raidstripealldevices." }, { "flag": "-I", "long": "--stripesize", "arg": null, "description": "The amount of data that is written to one device before moving to the next in a striped LV." }, { "flag": "-t", "long": "--test", "arg": null, "description": "Run 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 read‐ ing back metadata it believes has changed but hasn't." }, { "flag": "-T", "long": "--thin", "arg": null, "description": "Specifies the command is handling a thin LV or thin pool. See --type thin, --type thin-pool, and --virtualsize. See lvmthin(7) for more information about LVM thin pro‐ visioning. --thinpool LV The name of a thin pool LV. --type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo|vdo-pool|cache|cache-pool| writecache The 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 per‐ formance (raid, 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. For VDO (vdo) see lvmvdo(7). 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, --vdo). Use inferred types with care because it can lead to unexpected results." }, { "flag": "", "long": "--vdo", "arg": null, "description": "Specifies the command is handling VDO LV. See --type vdo. See lvmvdo(7) for more in‐ formation about VDO usage. --vdopool LV The name of a VDO pool LV. See lvmvdo(7) for more information about VDO usage. --vdosettings String Specifies tunable VDO options for VDO LVs. Use the form 'option=value' or 'op‐ tion1=value option2=value', or repeat --vdosettings for each option being set. These settings override the default VDO behaviors. To remove vdosettings and revert to the default VDO behaviors, use --vdosettings 'default'. See lvmvdo(7) for more informa‐ tion." }, { "flag": "-v", "long": "--verbose", "arg": null, "description": "Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr." }, { "flag": "", "long": "--version", "arg": null, "description": "Display version information." }, { "flag": "-V", "long": "--virtualsize", "arg": null, "description": "The virtual size of a new thin LV. See lvmthin(7) for more information about LVM thin provisioning. Using virtual size (-V) and actual size (-L) together creates a sparse LV. lvm.conf(5) global/sparsesegtypedefault determines the default segment type used to create a sparse LV. Anything written to a sparse LV will be returned when reading from it. Reading from other areas of the LV will return blocks of zeros. When using a snapshot to create a sparse LV, a hidden virtual device is created using the zero target, and the LV has the suffix vorigin. Snapshots are less efficient than thin provisioning when creating large sparse LVs (GiB)." }, { "flag": "-W", "long": "--wipesignatures", "arg": null, "description": "Controls detection and subsequent wiping of signatures on new LVs. There is a prompt for each signature detected to confirm its wiping (unless --yes is used to override confirmations.) When not specified, signatures are wiped whenever zeroing is done (see --zero). This behaviour can be configured with lvm.conf(5) allocation/wipesigna‐ tureswhenzeroingnewlvs. If blkid wiping is used (lvm.conf(5) alloca‐ tion/useblkidwiping) and LVM is compiled with blkid wiping support, then the blkid(8) library is used to detect the signatures (use blkid -k to list the signatures that are recognized). Otherwise, native LVM code is used to detect signatures (only MD RAID, swap and LUKS signatures are detected in this case.) The LV is not wiped if the read only flag is set." }, { "flag": "-y", "long": "--yes", "arg": null, "description": "Do not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)" }, { "flag": "-Z", "long": "--zero", "arg": null, "description": "Controls zeroing of the first 4KiB of data in the new LV. Default is y. Snapshot COW volumes are always zeroed. For thin pools, this controls zeroing of provisioned blocks. LV is not zeroed if the read only flag is set. Warning: trying to mount an unzeroed LV can cause the system to hang." } ], "examples": [ "Create a striped LV with 3 stripes, a stripe size of 8KiB and a size of 100MiB. The LV name", "is chosen by lvcreate.", "Create a raid1 LV with two images, and a useable size of 500 MiB. This operation requires two", "devices, one for each mirror image. RAID metadata (superblock and bitmap) is also included on", "the two devices.", "Create a mirror LV with two images, and a useable size of 500 MiB. This operation requires", "three devices: two for mirror images and one for a disk log.", "Create a mirror LV with 2 images, and a useable size of 500 MiB. This operation requires 2", "devices because the log is in memory.", "Create a copy-on-write snapshot of an LV:", "Create a copy-on-write snapshot with a size sufficient for overwriting 20% of the size of the", "original LV.", "Create a sparse LV with 1TiB of virtual space, and actual space just under 100MiB.", "Create a linear LV with a usable size of 64MiB on specific physical extents.", "Create a RAID5 LV with a usable size of 5GiB, 3 stripes, a stripe size of 64KiB, using a to‐", "tal of 4 devices (including one for parity).", "Create a RAID5 LV using all of the free space in the VG and spanning all the PVs in the VG", "(note that the command will fail if there are more than 8 PVs in the VG, in which case -i 7", "must be used to get to the current maximum of 8 devices including parity for RaidLVs).", "--type raid5 -l 100%FREE -n mylv vg00", "Create RAID10 LV with a usable size of 5GiB, using 2 stripes, each on a two-image mirror.", "(Note that the -i and -m arguments behave differently: -i specifies the total number of", "stripes, but -m specifies the number of images in addition to the first image).", "Create a 1TiB thin LV mythin, with 256GiB thinpool tpool0 in vg00.", "Create a 1TiB thin LV, first creating a new thin pool for it, where the thin pool has 100MiB", "of space, uses 2 stripes, has a 64KiB stripe size, and 256KiB chunk size.", "-V 1t -L 100m -i 2 -I 64 -c 256 vg00", "Create a thin snapshot of a thin LV (the size option must not be used, otherwise a copy-", "on-write snapshot would be created).", "Create a thin snapshot of the read-only inactive LV named \"origin\" which becomes an external", "origin for the thin snapshot LV.", "Create a cache pool from a fast physical device. The cache pool can then be used to cache an", "LV.", "Create a cache LV, first creating a new origin LV on a slow physical device, then combining", "the new origin LV with an existing cache pool.", "-L 100G -n mylv vg00 /dev/slow1", "Create a VDO LV vdo0 with VDOPoolLV size of 10GiB and name vpool1." ], "see_also": [ { "name": "lvm", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvm/8/json" }, { "name": "lvm.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/lvm.conf/5/json" }, { "name": "lvmconfig", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmconfig/8/json" }, { "name": "lvmdevices", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmdevices/8/json" }, { "name": "pvchange", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvchange/8/json" }, { "name": "pvck", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvck/8/json" }, { "name": "pvcreate", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvcreate/8/json" }, { "name": "pvdisplay", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvdisplay/8/json" }, { "name": "pvmove", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvmove/8/json" }, { "name": "pvremove", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvremove/8/json" }, { "name": "pvresize", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvresize/8/json" }, { "name": "pvs", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvs/8/json" }, { "name": "pvscan", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/pvscan/8/json" }, { "name": "vgcfgbackup", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgcfgbackup/8/json" }, { "name": "vgcfgrestore", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgcfgrestore/8/json" }, { "name": "vgchange", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgchange/8/json" }, { "name": "vgck", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgck/8/json" }, { "name": "vgcreate", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgcreate/8/json" }, { "name": "vgconvert", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgconvert/8/json" }, { "name": "vgdisplay", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgdisplay/8/json" }, { "name": "vgexport", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgexport/8/json" }, { "name": "vgextend", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgextend/8/json" }, { "name": "vgimport", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgimport/8/json" }, { "name": "vgimportclone", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgimportclone/8/json" }, { "name": "vgimportdevices", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgimportdevices/8/json" }, { "name": "vgmerge", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgmerge/8/json" }, { "name": "vgmknodes", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgmknodes/8/json" }, { "name": "vgreduce", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgreduce/8/json" }, { "name": "vgremove", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgremove/8/json" }, { "name": "vgrename", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgrename/8/json" }, { "name": "vgs", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgs/8/json" }, { "name": "vgscan", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgscan/8/json" }, { "name": "vgsplit", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/vgsplit/8/json" }, { "name": "lvchange", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvchange/8/json" }, { "name": "lvconvert", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvconvert/8/json" }, { "name": "lvdisplay", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvdisplay/8/json" }, { "name": "lvextend", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvextend/8/json" }, { "name": "lvreduce", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvreduce/8/json" }, { "name": "lvremove", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvremove/8/json" }, { "name": "lvrename", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvrename/8/json" }, { "name": "lvresize", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvresize/8/json" }, { "name": "lvs", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvs/8/json" }, { "name": "lvscan", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvscan/8/json" }, { "name": "lvm-fullreport", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvm-fullreport/8/json" }, { "name": "lvm-lvpoll", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvm-lvpoll/8/json" }, { "name": "blkdeactivate", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/blkdeactivate/8/json" }, { "name": "lvmdump", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmdump/8/json" }, { "name": "dmeventd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/dmeventd/8/json" }, { "name": "lvmpolld", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmpolld/8/json" }, { "name": "lvmlockd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmlockd/8/json" }, { "name": "lvmlockctl", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmlockctl/8/json" }, { "name": "cmirrord", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/cmirrord/8/json" }, { "name": "lvmdbusd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmdbusd/8/json" }, { "name": "fsadm", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/fsadm/8/json" }, { "name": "lvmsystemid", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/lvmsystemid/7/json" }, { "name": "lvmreport", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/lvmreport/7/json" }, { "name": "lvmraid", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/lvmraid/7/json" }, { "name": "lvmthin", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/lvmthin/7/json" }, { "name": "lvmcache", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/lvmcache/7/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 71, "subsections": [ { "name": "writecache", "lines": 10 } ] }, { "name": "DESCRIPTION", "lines": 27, "subsections": [ { "name": "Usage notes", "lines": 12 } ] }, { "name": "USAGE", "lines": 296, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-a --activate y", "lines": 27, "flag": "-a", "long": "--activate" }, { "name": "-A --autobackup y", "lines": 3, "flag": "-A", "long": "--autobackup" }, { "name": "-H --cache", "lines": 39, "flag": "-H", "long": "--cache" }, { "name": "-c --chunksize _", "lines": 21, "flag": "-c", "long": "--chunksize" }, { "name": "-C --contiguous y", "lines": 5, "flag": "-C", "long": "--contiguous" }, { "name": "-d --debug", "lines": 36, "flag": "-d", "long": "--debug" }, { "name": "-l --extents _", "lines": 12, "flag": "-l", "long": "--extents" }, { "name": "-h --help", "lines": 2, "flag": "-h", "long": "--help" }, { "name": "-K --ignoreactivationskip", "lines": 3, "flag": "-K", "long": "--ignoreactivationskip" }, { "name": "--ignoremonitoring", "lines": 13, "long": "--ignoremonitoring" }, { "name": "--longhelp", "lines": 2, "long": "--longhelp" }, { "name": "-j --major _", "lines": 28, "flag": "-j", "long": "--major" }, { "name": "-m --mirrors _", "lines": 15, "flag": "-m", "long": "--mirrors" }, { "name": "-n --name _", "lines": 3, "flag": "-n", "long": "--name" }, { "name": "--nohints", "lines": 4, "long": "--nohints" }, { "name": "--nolocking", "lines": 3, "long": "--nolocking" }, { "name": "--nosync", "lines": 11, "long": "--nosync" }, { "name": "--noudevsync", "lines": 4, "long": "--noudevsync" }, { "name": "-p --permission rw", "lines": 2, "flag": "-p", "long": "--permission" }, { "name": "-M --persistent y", "lines": 13, "flag": "-M", "long": "--persistent" }, { "name": "-q --quiet", "lines": 20, "flag": "-q", "long": "--quiet" }, { "name": "-r --readahead auto", "lines": 3, "flag": "-r", "long": "--readahead" }, { "name": "-R --regionsize _", "lines": 10, "flag": "-R", "long": "--regionsize" }, { "name": "-k --setactivationskip y", "lines": 14, "flag": "-k", "long": "--setactivationskip" }, { "name": "-L --size _", "lines": 4, "flag": "-L", "long": "--size" }, { "name": "-s --snapshot", "lines": 19, "flag": "-s", "long": "--snapshot" }, { "name": "-i --stripes _", "lines": 10, "flag": "-i", "long": "--stripes" }, { "name": "-I --stripesize _", "lines": 3, "flag": "-I", "long": "--stripesize" }, { "name": "-t --test", "lines": 5, "flag": "-t", "long": "--test" }, { "name": "-T --thin", "lines": 19, "flag": "-T", "long": "--thin" }, { "name": "--vdo", "lines": 13, "long": "--vdo" }, { "name": "-v --verbose", "lines": 3, "flag": "-v", "long": "--verbose" }, { "name": "--version", "lines": 2, "long": "--version" }, { "name": "-V --virtualsize _", "lines": 9, "flag": "-V", "long": "--virtualsize" }, { "name": "-W --wipesignatures y", "lines": 11, "flag": "-W", "long": "--wipesignatures" }, { "name": "-y --yes", "lines": 3, "flag": "-y", "long": "--yes" }, { "name": "-Z --zero y", "lines": 5, "flag": "-Z", "long": "--zero" } ] }, { "name": "VARIABLES", "lines": 25, "subsections": [] }, { "name": "ENVIRONMENT VARIABLES", "lines": 3, "subsections": [] }, { "name": "ADVANCED USAGE", "lines": 397, "subsections": [] }, { "name": "EXAMPLES", "lines": 2, "subsections": [ { "name": "lvcreate -i 3 -I 8 -L 100m vg00", "lines": 3 }, { "name": "lvcreate --type raid1 -m1 -L 500m -n mylv vg00", "lines": 2 }, { "name": "lvcreate --type mirror -m1 -L 500m -n mylv vg00", "lines": 2 }, { "name": "lvcreate --type mirror -m1 --mirrorlog core -L 500m -n mylv vg00", "lines": 1 }, { "name": "lvcreate --snapshot --size 100m --name mysnap vg00/mylv", "lines": 2 }, { "name": "lvcreate -s -l 20%ORIGIN -n mysnap vg00/mylv", "lines": 1 }, { "name": "lvcreate --snapshot --virtualsize 1t --size 100m --name mylv vg00", "lines": 1 }, { "name": "lvcreate -L 64m -n mylv vg00 /dev/sda:0-7 /dev/sdb:0-7", "lines": 2 }, { "name": "lvcreate --type raid5 -L 5G -i 3 -I 64 -n mylv vg00", "lines": 3 }, { "name": "lvcreate --config allocation/raid_stripe_all_devices=1", "lines": 5 }, { "name": "lvcreate --type raid10 -L 5G -i 2 -m 1 -n mylv vg00", "lines": 1 }, { "name": "lvcreate -T -V 1T --size 256G --name mythin vg00/tpool0", "lines": 2 }, { "name": "lvcreate --type thin --name mylv --thinpool mypool", "lines": 4 }, { "name": "lvcreate --snapshot --name mysnap vg00/thinvol", "lines": 2 }, { "name": "lvcreate --snapshot --name mysnap --thinpool mypool vg00/origin", "lines": 2 }, { "name": "lvcreate --type cache-pool -L 1G -n my_cpool vg00 /dev/fast1", "lines": 2 }, { "name": "lvcreate --type cache --cachepool my_cpool", "lines": 3 }, { "name": "lvcreate --vdo --size 10G --name vdo0 vg00/vpool1", "lines": 1 } ] }, { "name": "SEE ALSO", "lines": 20, "subsections": [] } ], "sections": { "NAME": { "content": "lvcreate — Create a logical volume\n", "subsections": [] }, "SYNOPSIS": { "content": "lvcreate optionargs positionargs\n[ optionargs ]\n[ positionargs ]\n\n-a|--activate y|n|ay\n--addtag Tag\n--alloc contiguous|cling|clingbytags|normal|anywhere|inherit\n-A|--autobackup y|n\n-H|--cache\n--cachedevice PV\n--cachemetadataformat auto|1|2\n--cachemode writethrough|writeback|passthrough\n--cachepolicy String\n--cachepool LV\n--cachesettings String\n--cachesize Size[m|UNIT]\n--cachevol LV\n-c|--chunksize Size[k|UNIT]\n--commandprofile String\n--compression y|n\n--config String\n-C|--contiguous y|n\n-d|--debug\n--deduplication y|n\n--devices PV\n--devicesfile String\n--discards passdown|nopassdown|ignore\n--driverloaded y|n\n--errorwhenfull y|n\n-l|--extents Number[PERCENT]\n-h|--help\n-K|--ignoreactivationskip\n--ignoremonitoring\n--journal String\n--lockopt String\n--longhelp\n-j|--major Number\n--[raid]maxrecoveryrate Size[k|UNIT]\n--metadataprofile String\n--minor Number\n--[raid]minrecoveryrate Size[k|UNIT]\n--mirrorlog core|disk\n-m|--mirrors Number\n--monitor y|n\n-n|--name String\n--nohints\n--nolocking\n--nosync\n--noudevsync\n-p|--permission rw|r\n-M|--persistent y|n\n--poolmetadatasize Size[m|UNIT]\n--poolmetadataspare y|n\n--profile String\n-q|--quiet\n--raidintegrity y|n\n--raidintegrityblocksize Number\n--raidintegritymode String\n-r|--readahead auto|none|Number\n-R|--regionsize Size[m|UNIT]\n--reportformat basic|json\n-k|--setactivationskip y|n\n--setautoactivation y|n\n-L|--size Size[m|UNIT]\n-s|--snapshot\n-i|--stripes Number\n-I|--stripesize Size[k|UNIT]\n-t|--test\n-T|--thin\n--thinpool LV\n--type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo|vdo-pool|cache|cache-pool|", "subsections": [ { "name": "writecache", "content": "--vdo\n--vdopool LV\n--vdosettings String\n-v|--verbose\n--version\n-V|--virtualsize Size[m|UNIT]\n-W|--wipesignatures y|n\n-y|--yes\n-Z|--zero y|n\n" } ] }, "DESCRIPTION": { "content": "lvcreate creates a new LV in a VG. For standard LVs, this requires allocating logical extents\nfrom the VG's free physical extents. If there is not enough free space, the VG can be extend‐\ned with other PVs (vgextend(8)), or existing LVs can be reduced or removed (lvremove(8),\nlvreduce(8)).\n\nTo control which PVs a new LV will use, specify one or more PVs as position args at the end\nof the command line. lvcreate will allocate physical extents only from the specified PVs.\n\nlvcreate can also create snapshots of existing LVs, e.g. for backup purposes. The data in a\nnew snapshot LV represents the content of the original LV from the time the snapshot was cre‐\nated.\n\nRAID LVs can be created by specifying an LV type when creating the LV (see lvmraid(7)). Dif‐\nferent RAID levels require different numbers of unique PVs be available in the VG for alloca‐\ntion.\n\nThin pools (for thin provisioning) and cache pools (for caching) are represented by special\nLVs with types thin-pool and cache-pool (see lvmthin(7) and lvmcache(7)). The pool LVs are\nnot usable as standard block devices, but the LV names act as references to the pools.\n\nThin LVs are thinly provisioned from a thin pool, and are created with a virtual size rather\nthan a physical size. A cache LV is the combination of a standard LV with a cache pool, used\nto cache active portions of the LV to improve performance.\n\nVDO LVs are also provisioned volumes from a VDO pool, and are created with a virtual size\nrather than a physical size (see lvmvdo(7)).\n", "subsections": [ { "name": "Usage notes", "content": "In the usage section below, --size Size can be replaced with --extents Number. See descrip‐\ntions in the options section.\n\nIn the usage section below, --name is omitted from the required options, even though it is\ntypically used. When the name is not specified, a new LV name is generated with the \"lvol\"\nprefix and a unique numeric suffix.\n\nIn the usage section below, when creating a pool and the name is omitted the new LV pool name\nis generated with the \"vpool\" for vdo-pools for prefix and a unique numeric suffix.\n\nPool name can be specified together with VG name i.e.: vg00/mythinpool.\n" } ] }, "USAGE": { "content": "Create a linear LV.\n\nlvcreate -L|--size Size[m|UNIT] VG\n[ --type linear ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a striped LV.\n\nlvcreate -i|--stripes Number -L|--size Size[m|UNIT] VG\n[ --type striped ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a raid1 or mirror LV.\n\nlvcreate -m|--mirrors Number -L|--size Size[m|UNIT] VG\n[ --type raid1|mirror ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -R|--regionsize Size[m|UNIT] ]\n[ --mirrorlog core|disk ]\n[ --[raid]minrecoveryrate Size[k|UNIT] ]\n[ --[raid]maxrecoveryrate Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a raid LV (a specific raid level must be used, e.g. raid1).\n\nlvcreate --type raid -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -m|--mirrors Number ]\n[ -R|--regionsize Size[m|UNIT] ]\n[ --[raid]minrecoveryrate Size[k|UNIT] ]\n[ --[raid]maxrecoveryrate Size[k|UNIT] ]\n[ --raidintegrity y|n ]\n[ --raidintegritymode String ]\n[ --raidintegrityblocksize Number ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a raid10 LV.\n\nlvcreate -m|--mirrors Number -i|--stripes Number\n-L|--size Size[m|UNIT] VG\n[ --type raid10 ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -R|--regionsize Size[m|UNIT] ]\n[ --[raid]minrecoveryrate Size[k|UNIT] ]\n[ --[raid]maxrecoveryrate Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a COW snapshot LV of an origin LV.\n\nlvcreate -s|--snapshot -L|--size Size[m|UNIT] LV\n[ --type snapshot ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin pool.\n\nlvcreate --type thin-pool -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --thinpool LVnew ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a cache pool.\n\nlvcreate --type cache-pool -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -H|--cache ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV in a thin pool.\n\nlvcreate -V|--virtualsize Size[m|UNIT] --thinpool LV VG\n[ --type thin ] (implied)\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\n—\n\nCreate a thin LV that is a snapshot of an existing thin LV.\n\nlvcreate -s|--snapshot LV1\n[ --type thin ] (implied)\n[ COMMONOPTIONS ]\n\nLV1 types: thin\n\n—\n\nCreate a thin LV that is a snapshot of an external origin LV.\n\nlvcreate --type thin --thinpool LV LV\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\n—\n\nCreate a LV that returns VDO when used.\n\nlvcreate --type vdo -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -V|--virtualsize Size[m|UNIT] ]\n[ --vdo ]\n[ --vdopool LVnew ]\n[ --compression y|n ]\n[ --deduplication y|n ]\n[ --vdosettings String ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach the specified cachepool\nwhich converts the new LV to type cache.\n\nlvcreate --type cache -L|--size Size[m|UNIT]\n--cachepool LV VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -H|--cache ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach the specified cachevol\nwhich converts the new LV to type cache.\n\nlvcreate --type cache -L|--size Size[m|UNIT]\n--cachevol LV VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach a cachevol created from\nthe specified cache device, which converts the\nnew LV to type cache.\n\nlvcreate --type cache -L|--size Size[m|UNIT]\n--cachedevice PV VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachesize Size[m|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach the specified cachevol\nwhich converts the new LV to type writecache.\n\nlvcreate --type writecache -L|--size Size[m|UNIT]\n--cachevol LV VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ --cachesettings String ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach a cachevol created from\nthe specified cache device, which converts the\nnew LV to type writecache.\n\nlvcreate --type writecache -L|--size Size[m|UNIT]\n--cachedevice PV VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ --cachesize Size[m|UNIT] ]\n[ --cachesettings String ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCommon options for command:\n[ -a|--activate y|n|ay ]\n[ -A|--autobackup y|n ]\n[ -C|--contiguous y|n ]\n[ -K|--ignoreactivationskip ]\n[ -j|--major Number ]\n[ -n|--name String ]\n[ -p|--permission rw|r ]\n[ -M|--persistent y|n ]\n[ -r|--readahead auto|none|Number ]\n[ -k|--setactivationskip y|n ]\n[ -W|--wipesignatures y|n ]\n[ -Z|--zero y|n ]\n[ --addtag Tag ]\n[ --alloc contiguous|cling|clingbytags|normal|anywhere|inherit ]\n[ --ignoremonitoring ]\n[ --metadataprofile String ]\n[ --minor Number ]\n[ --monitor y|n ]\n[ --nosync ]\n[ --noudevsync ]\n[ --reportformat basic|json ]\n[ --setautoactivation y|n ]\n\nCommon options for lvm:\n[ -d|--debug ]\n[ -h|--help ]\n[ -q|--quiet ]\n[ -t|--test ]\n[ -v|--verbose ]\n[ -y|--yes ]\n[ --commandprofile String ]\n[ --config String ]\n[ --devices PV ]\n[ --devicesfile String ]\n[ --driverloaded y|n ]\n[ --journal String ]\n[ --lockopt String ]\n[ --longhelp ]\n[ --nohints ]\n[ --nolocking ]\n[ --profile String ]\n[ --version ]\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-a --activate y", "content": "Controls the active state of the new LV. y makes the LV active, or available. New\nLVs are made active by default. n makes the LV inactive, or unavailable, only when\npossible. In some cases, creating an LV requires it to be active. For example, COW\nsnapshots of an active origin LV can only be created in the active state (this does\nnot apply to thin snapshots). The --zero option normally requires the LV to be ac‐\ntive. If autoactivation ay is used, the LV is only activated if it matches an item in\nlvm.conf(5) activation/autoactivationvolumelist. ay implies --zero n and --wipes‐\nignatures n. See lvmlockd(8) for more information about activation options for shared\nVGs.\n\n--addtag Tag\nAdds a tag to a PV, VG or LV. This option can be repeated to add multiple tags at\nonce. See lvm(8) for information about tags.\n\n--alloc contiguous|cling|clingbytags|normal|anywhere|inherit\nDetermines the allocation policy when a command needs to allocate Physical Extents\n(PEs) from the VG. Each VG and LV has an allocation policy which can be changed with\nvgchange/lvchange, or overridden on the command line. normal applies common sense\nrules such as not placing parallel stripes on the same PV. inherit applies the VG\npolicy to an LV. contiguous requires new PEs be placed adjacent to existing PEs.\ncling places new PEs on the same PV as existing PEs in the same stripe of the LV. If\nthere are sufficient PEs for an allocation, but normal does not use them, anywhere\nwill use them even if it reduces performance, e.g. by placing two stripes on the same\nPV. Optional positional PV args on the command line can also be used to limit which\nPVs the command will use for allocation. See lvm(8) for more information about allo‐\ncation.\n", "flag": "-a", "long": "--activate" }, { "name": "-A --autobackup y", "content": "Specifies if metadata should be backed up automatically after a change. Enabling this\nis strongly advised! See vgcfgbackup(8) for more information.\n", "flag": "-A", "long": "--autobackup" }, { "name": "-H --cache", "content": "Specifies the command is handling a cache LV or cache pool. See --type cache and\n--type cache-pool. See lvmcache(7) for more information about LVM caching.\n\n--cachedevice PV\nThe name of a device to use for a cache.\n\n--cachemetadataformat auto|1|2\nSpecifies the cache metadata format used by cache target.\n\n--cachemode writethrough|writeback|passthrough\nSpecifies when writes to a cache LV should be considered complete. writeback consid‐\ners a write complete as soon as it is stored in the cache pool. writethough considers\na write complete only when it has been stored in both the cache pool and on the origin\nLV. While writethrough may be slower for writes, it is more resilient if something\nshould happen to a device associated with the cache pool LV. With passthrough, all\nreads are served from the origin LV (all reads miss the cache) and all writes are for‐\nwarded to the origin LV; additionally, write hits cause cache block invalidates. See\nlvmcache(7) for more information.\n\n--cachepolicy String\nSpecifies the cache policy for a cache LV. See lvmcache(7) for more information.\n\n--cachepool LV\nThe name of a cache pool.\n\n--cachesettings String\nSpecifies tunable kernel options for dm-cache or dm-writecache LVs. Use the form 'op‐\ntion=value' or 'option1=value option2=value', or repeat --cachesettings for each op‐\ntion being set. These settings override the default kernel behaviors which are usual‐\nly adequate. To remove cachesettings and revert to the default kernel behaviors, use\n--cachesettings 'default' for dm-cache or an empty string --cachesettings '' for dm-\nwritecache. See lvmcache(7) for more information.\n\n--cachesize Size[m|UNIT]\nThe size of cache to use.\n\n--cachevol LV\nThe name of a cache volume.\n", "flag": "-H", "long": "--cache" }, { "name": "-c --chunksize _", "content": "The size of chunks in a snapshot, cache pool or thin pool. For snapshots, the value\nmust be a power of 2 between 4KiB and 512KiB and the default value is 4. For a cache\npool the value must be between 32KiB and 1GiB and the default value is 64. For a thin\npool the value must be between 64KiB and 1GiB and the default value starts with 64 and\nscales up to fit the pool metadata size within 128MiB, if the pool metadata size is\nnot specified. The value must be a multiple of 64KiB. See lvmthin(7) and lvmcache(7)\nfor more information.\n\n--commandprofile String\nThe command profile to use for command configuration. See lvm.conf(5) for more infor‐\nmation about profiles.\n\n--compression y|n\nControls whether compression is enabled or disable for VDO volume. See lvmvdo(7) for\nmore information about VDO usage.\n\n--config String\nConfig settings for the command. These override lvm.conf(5) settings. The String arg\nuses the same format as lvm.conf(5), or may use section/field syntax. See lvm.conf(5)\nfor more information about config.\n", "flag": "-c", "long": "--chunksize" }, { "name": "-C --contiguous y", "content": "Sets or resets the contiguous allocation policy for LVs. Default is no contiguous al‐\nlocation based on a next free principle. It is only possible to change a non-contigu‐\nous allocation policy to contiguous if all of the allocated physical extents in the LV\nare already contiguous.\n", "flag": "-C", "long": "--contiguous" }, { "name": "-d --debug", "content": "Set debug level. Repeat from 1 to 6 times to increase the detail of messages sent to\nthe log file and/or syslog (if configured).\n\n--deduplication y|n\nControls whether deduplication is enabled or disable for VDO volume. See lvmvdo(7)\nfor more information about VDO usage.\n\n--devices PV\nRestricts the devices that are visible and accessible to the command. Devices not\nlisted will appear to be missing. This option can be repeated, or accepts a comma sep‐\narated list of devices. This overrides the devices file.\n\n--devicesfile String\nA file listing devices that LVM should use. The file must exist in /etc/lvm/devices/\nand is managed with the lvmdevices(8) command. This overrides the lvm.conf(5) de‐\nvices/devicesfile and devices/usedevicesfile settings.\n\n--discards passdown|nopassdown|ignore\nSpecifies how the device-mapper thin pool layer in the kernel should handle discards.\nignore causes the thin pool to ignore discards. nopassdown causes the thin pool to\nprocess discards itself to allow reuse of unneeded extents in the thin pool. passdown\ncauses the thin pool to process discards itself (like nopassdown) and pass the dis‐\ncards to the underlying device. See lvmthin(7) for more information.\n\n--driverloaded y|n\nIf set to no, the command will not attempt to use device-mapper. For testing and de‐\nbugging.\n\n--errorwhenfull y|n\nSpecifies thin pool behavior when data space is exhausted. When yes, device-mapper\nwill immediately return an error when a thin pool is full and an I/O request requires\nspace. When no, device-mapper will queue these I/O requests for a period of time to\nallow the thin pool to be extended. Errors are returned if no space is available af‐\nter the timeout. (Also see dm-thin-pool kernel module option nospacetimeout.) See\nlvmthin(7) for more information.\n", "flag": "-d", "long": "--debug" }, { "name": "-l --extents _", "content": "Specifies the size of the new LV in logical extents. The --size and --extents options\nare alternate methods of specifying size. The total number of physical extents used\nwill be greater when redundant data is needed for RAID levels. An alternate syntax\nallows the size to be determined indirectly as a percentage of the size of a related\nVG, LV, or set of PVs. The suffix %VG denotes the total size of the VG, the suffix\n%FREE the remaining free space in the VG, and the suffix %PVS the free space in the\nspecified PVs. For a snapshot, the size can be expressed as a percentage of the total\nsize of the origin LV with the suffix %ORIGIN (100%ORIGIN provides space for the whole\norigin). When expressed as a percentage, the size defines an upper limit for the num‐\nber of logical extents in the new LV. The precise number of logical extents in the new\nLV is not determined until the command has completed.\n", "flag": "-l", "long": "--extents" }, { "name": "-h --help", "content": "Display help text.\n", "flag": "-h", "long": "--help" }, { "name": "-K --ignoreactivationskip", "content": "Ignore the \"activation skip\" LV flag during activation to allow LVs with the flag set\nto be activated.\n", "flag": "-K", "long": "--ignoreactivationskip" }, { "name": "--ignoremonitoring", "content": "Do not interact with dmeventd unless --monitor is specified. Do not use this if\ndmeventd is already monitoring a device.\n\n--journal String\nRecord information in the systemd journal. This information is in addition to infor‐\nmation enabled by the lvm.conf log/journal setting. command: record information about\nthe command. output: record the default command output. debug: record full command\ndebugging.\n\n--lockopt String\nUsed to pass options for special cases to lvmlockd. See lvmlockd(8) for more informa‐\ntion.\n", "long": "--ignoremonitoring" }, { "name": "--longhelp", "content": "Display long help text.\n", "long": "--longhelp" }, { "name": "-j --major _", "content": "Sets the major number of an LV block device.\n\n--[raid]maxrecoveryrate Size[k|UNIT]\nSets the maximum recovery rate for a RAID LV. The rate value is an amount of data per\nsecond for each device in the array. Setting the rate to 0 means it will be unbound‐\ned. See lvmraid(7) for more information.\n\n--metadataprofile String\nThe metadata profile to use for command configuration. See lvm.conf(5) for more in‐\nformation about profiles.\n\n--minor Number\nSets the minor number of an LV block device.\n\n--[raid]minrecoveryrate Size[k|UNIT]\nSets the minimum recovery rate for a RAID LV. The rate value is an amount of data per\nsecond for each device in the array. Setting the rate to 0 means it will be unbound‐\ned. See lvmraid(7) for more information.\n\n--mirrorlog core|disk\nSpecifies the type of mirror log for LVs with the \"mirror\" type (does not apply to the\n\"raid1\" type.) disk is a persistent log and requires a small amount of storage space,\nusually on a separate device from the data being mirrored. core is not persistent;\nthe log is kept only in memory. In this case, the mirror must be synchronized (by\ncopying LV data from the first device to others) each time the LV is activated, e.g.\nafter reboot. mirrored is a persistent log that is itself mirrored, but should be\navoided. Instead, use the raid1 type for log redundancy.\n", "flag": "-j", "long": "--major" }, { "name": "-m --mirrors _", "content": "Specifies the number of mirror images in addition to the original LV image, e.g.\n--mirrors 1 means there are two images of the data, the original and one mirror image.\nOptional positional PV args on the command line can specify the devices the images\nshould be placed on. There are two mirroring implementations: \"raid1\" and \"mirror\".\nThese are the names of the corresponding LV types, or \"segment types\". Use the --type\noption to specify which to use (raid1 is default, and mirror is legacy) Use\nlvm.conf(5) global/mirrorsegtypedefault and global/raid10segtypedefault to config‐\nure the default types. See the --nosync option for avoiding initial image synchro‐\nnization. See lvmraid(7) for more information.\n\n--monitor y|n\nStart (yes) or stop (no) monitoring an LV with dmeventd. dmeventd monitors kernel\nevents for an LV, and performs automated maintenance for the LV in reponse to specific\nevents. See dmeventd(8) for more information.\n", "flag": "-m", "long": "--mirrors" }, { "name": "-n --name _", "content": "Specifies the name of a new LV. When unspecified, a default name of \"lvol#\" is gener‐\nated, where # is a number generated by LVM.\n", "flag": "-n", "long": "--name" }, { "name": "--nohints", "content": "Do not use the hints file to locate devices for PVs. A command may read more devices\nto find PVs when hints are not used. The command will still perform standard hint file\ninvalidation where appropriate.\n", "long": "--nohints" }, { "name": "--nolocking", "content": "Disable locking. Use with caution, concurrent commands may produce incorrect results.\n\n", "long": "--nolocking" }, { "name": "--nosync", "content": "Causes the creation of mirror, raid1, raid4, raid5 and raid10 to skip the initial syn‐\nchronization. In case of mirror, raid1 and raid10, any data written afterwards will be\nmirrored, but the original contents will not be copied. In case of raid4 and raid5, no\nparity blocks will be written, though any data written afterwards will cause parity\nblocks to be stored. This is useful for skipping a potentially long and resource in‐\ntensive initial sync of an empty mirror/raid1/raid4/raid5 and raid10 LV. This option\nis not valid for raid6, because raid6 relies on proper parity (P and Q Syndromes) be‐\ning created during initial synchronization in order to reconstruct proper user date in\ncase of device failures. raid0 and raid0meta do not provide any data copies or pari‐\nty support and thus do not support initial synchronization.\n", "long": "--nosync" }, { "name": "--noudevsync", "content": "Disables udev synchronisation. The process will not wait for notification from udev.\nIt will continue irrespective of any possible udev processing in the background. Only\nuse this if udev is not running or has rules that ignore the devices LVM creates.\n", "long": "--noudevsync" }, { "name": "-p --permission rw", "content": "Set access permission to read only r or read and write rw.\n", "flag": "-p", "long": "--permission" }, { "name": "-M --persistent y", "content": "When yes, makes the specified minor number persistent.\n\n--poolmetadatasize Size[m|UNIT]\nSpecifies the size of the new pool metadata LV.\n\n--poolmetadataspare y|n\nEnable or disable the automatic creation and management of a spare pool metadata LV in\nthe VG. A spare metadata LV is reserved space that can be used when repairing a pool.\n\n\n--profile String\nAn alias for --commandprofile or --metadataprofile, depending on the command.\n", "flag": "-M", "long": "--persistent" }, { "name": "-q --quiet", "content": "Suppress output and log messages. Overrides --debug and --verbose. Repeat once to al‐\nso suppress any prompts with answer 'no'.\n\n--raidintegrity y|n\nEnable or disable data integrity checksums for raid images.\n\n--raidintegrityblocksize Number\nThe block size to use for dm-integrity on raid images. The integrity block size\nshould usually match the device logical block size, or the file system block size. It\nmay be less than the file system block size, but not less than the device logical\nblock size. Possible values: 512, 1024, 2048, 4096.\n\n--raidintegritymode String\nUse a journal (default) or bitmap for keeping integrity checksums consistent in case\nof a crash. The bitmap areas are recalculated after a crash, so corruption in those\nareas would not be detected. A journal does not have this problem. The journal mode\ndoubles writes to storage, but can improve performance for scattered writes packed in‐\nto a single journal write. bitmap mode can in theory achieve full write throughput of\nthe device, but would not benefit from the potential scattered write optimization.\n", "flag": "-q", "long": "--quiet" }, { "name": "-r --readahead auto", "content": "Sets read ahead sector count of an LV. auto is the default which allows the kernel to\nchoose a suitable value automatically. none is equivalent to zero.\n", "flag": "-r", "long": "--readahead" }, { "name": "-R --regionsize _", "content": "Size of each raid or mirror synchronization region. lvm.conf(5) activation/raidre‐\ngionsize can be used to configure a default.\n\n--reportformat basic|json\nOverrides current output format for reports which is defined globally by the re‐\nport/outputformat setting in lvm.conf(5). basic is the original format with columns\nand rows. If there is more than one report per command, each report is prefixed with\nthe report name for identification. json produces report output in JSON format. See\nlvmreport(7) for more information.\n", "flag": "-R", "long": "--regionsize" }, { "name": "-k --setactivationskip y", "content": "Persistently sets (yes) or clears (no) the \"activation skip\" flag on an LV. An LV\nwith this flag set is not activated unless the --ignoreactivationskip option is used\nby the activation command. This flag is set by default on new thin snapshot LVs. The\nflag is not applied to deactivation. The current value of the flag is indicated in\nthe lvs lvattr bits.\n\n--setautoactivation y|n\nSet the autoactivation property on a VG or LV. Display the property with vgs or lvs\n\"-o autoactivation\". When the autoactivation property is disabled, the VG or LV will\nnot be activated by a command doing autoactivation (vgchange, lvchange, or pvscan us‐\ning -aay.) If autoactivation is disabled on a VG, no LVs will be autoactivated in\nthat VG, and the LV autoactivation property has no effect. If autoactivation is en‐\nabled on a VG, autoactivation can be disabled for individual LVs.\n", "flag": "-k", "long": "--setactivationskip" }, { "name": "-L --size _", "content": "Specifies the size of the new LV. The --size and --extents options are alternate\nmethods of specifying size. The total number of physical extents used will be greater\nwhen redundant data is needed for RAID levels.\n", "flag": "-L", "long": "--size" }, { "name": "-s --snapshot", "content": "Create a snapshot. Snapshots provide a \"frozen image\" of an origin LV. The snapshot\nLV can be used, e.g. for backups, while the origin LV continues to be used. This op‐\ntion can create a COW (copy on write) snapshot, or a thin snapshot (in a thin pool.)\nThin snapshots are created when the origin is a thin LV and the size option is NOT\nspecified. Thin snapshots share the same blocks in the thin pool, and do not allocate\nnew space from the VG. Thin snapshots are created with the \"activation skip\" flag,\nsee --setactivationskip. A thin snapshot of a non-thin \"external origin\" LV is creat‐\ned when a thin pool is specified. Unprovisioned blocks in the thin snapshot LV are\nread from the external origin LV. The external origin LV must be read-only. See\nlvmthin(7) for more information about LVM thin provisioning. COW snapshots are creat‐\ned when a size is specified. The size is allocated from space in the VG, and is the\namount of space that can be used for saving COW blocks as writes occur to the origin\nor snapshot. The size chosen should depend upon the amount of writes that are expect‐\ned; often 20% of the origin LV is enough. If COW space runs low, it can be extended\nwith lvextend (shrinking is also allowed with lvreduce.) A small amount of the COW\nsnapshot LV size is used to track COW block locations, so the full size is not avail‐\nable for COW data blocks. Use lvs to check how much space is used, and see --monitor\nto to automatically extend the size to avoid running out of space.\n", "flag": "-s", "long": "--snapshot" }, { "name": "-i --stripes _", "content": "Specifies the number of stripes in a striped LV. This is the number of PVs (devices)\nthat a striped LV is spread across. Data that appears sequential in the LV is spread\nacross multiple devices in units of the stripe size (see --stripesize). This does not\nchange existing allocated space, but only applies to space being allocated by the com‐\nmand. When creating a RAID 4/5/6 LV, this number does not include the extra devices\nthat are required for parity. The largest number depends on the RAID type (raid0: 64,\nraid10: 32, raid4/5: 63, raid6: 62), and when unspecified, the default depends on the\nRAID type (raid0: 2, raid10: 2, raid4/5: 3, raid6: 5.) To stripe a new raid LV across\nall PVs by default, see lvm.conf(5) allocation/raidstripealldevices.\n", "flag": "-i", "long": "--stripes" }, { "name": "-I --stripesize _", "content": "The amount of data that is written to one device before moving to the next in a\nstriped LV.\n", "flag": "-I", "long": "--stripesize" }, { "name": "-t --test", "content": "Run in test mode. Commands will not update metadata. This is implemented by disabling\nall metadata writing but nevertheless returning success to the calling function. This\nmay lead to unusual error messages in multi-stage operations if a tool relies on read‐\ning back metadata it believes has changed but hasn't.\n", "flag": "-t", "long": "--test" }, { "name": "-T --thin", "content": "Specifies the command is handling a thin LV or thin pool. See --type thin, --type\nthin-pool, and --virtualsize. See lvmthin(7) for more information about LVM thin pro‐\nvisioning.\n\n--thinpool LV\nThe name of a thin pool LV.\n\n--type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo|vdo-pool|cache|cache-pool|\nwritecache\nThe LV type, also known as \"segment type\" or \"segtype\". See usage descriptions for\nthe specific ways to use these types. For more information about redundancy and per‐\nformance (raid, mirror, striped, linear) see lvmraid(7). For thin provisioning\n(thin, thin-pool) see lvmthin(7). For performance caching (cache, cache-pool) see\nlvmcache(7). For copy-on-write snapshots (snapshot) see usage definitions. For VDO\n(vdo) see lvmvdo(7). Several commands omit an explicit type option because the type\nis inferred from other options or shortcuts (e.g. --stripes, --mirrors, --snapshot,\n--virtualsize, --thin, --cache, --vdo). Use inferred types with care because it can\nlead to unexpected results.\n", "flag": "-T", "long": "--thin" }, { "name": "--vdo", "content": "Specifies the command is handling VDO LV. See --type vdo. See lvmvdo(7) for more in‐\nformation about VDO usage.\n\n--vdopool LV\nThe name of a VDO pool LV. See lvmvdo(7) for more information about VDO usage.\n\n--vdosettings String\nSpecifies tunable VDO options for VDO LVs. Use the form 'option=value' or 'op‐\ntion1=value option2=value', or repeat --vdosettings for each option being set. These\nsettings override the default VDO behaviors. To remove vdosettings and revert to the\ndefault VDO behaviors, use --vdosettings 'default'. See lvmvdo(7) for more informa‐\ntion.\n", "long": "--vdo" }, { "name": "-v --verbose", "content": "Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to\nstdout and stderr.\n", "flag": "-v", "long": "--verbose" }, { "name": "--version", "content": "Display version information.\n", "long": "--version" }, { "name": "-V --virtualsize _", "content": "The virtual size of a new thin LV. See lvmthin(7) for more information about LVM thin\nprovisioning. Using virtual size (-V) and actual size (-L) together creates a sparse\nLV. lvm.conf(5) global/sparsesegtypedefault determines the default segment type\nused to create a sparse LV. Anything written to a sparse LV will be returned when\nreading from it. Reading from other areas of the LV will return blocks of zeros.\nWhen using a snapshot to create a sparse LV, a hidden virtual device is created using\nthe zero target, and the LV has the suffix vorigin. Snapshots are less efficient\nthan thin provisioning when creating large sparse LVs (GiB).\n", "flag": "-V", "long": "--virtualsize" }, { "name": "-W --wipesignatures y", "content": "Controls detection and subsequent wiping of signatures on new LVs. There is a prompt\nfor each signature detected to confirm its wiping (unless --yes is used to override\nconfirmations.) When not specified, signatures are wiped whenever zeroing is done\n(see --zero). This behaviour can be configured with lvm.conf(5) allocation/wipesigna‐\ntureswhenzeroingnewlvs. If blkid wiping is used (lvm.conf(5) alloca‐\ntion/useblkidwiping) and LVM is compiled with blkid wiping support, then the\nblkid(8) library is used to detect the signatures (use blkid -k to list the signatures\nthat are recognized). Otherwise, native LVM code is used to detect signatures (only\nMD RAID, swap and LUKS signatures are detected in this case.) The LV is not wiped if\nthe read only flag is set.\n", "flag": "-W", "long": "--wipesignatures" }, { "name": "-y --yes", "content": "Do not prompt for confirmation interactively but always assume the answer yes. Use\nwith extreme caution. (For automatic no, see -qq.)\n", "flag": "-y", "long": "--yes" }, { "name": "-Z --zero y", "content": "Controls zeroing of the first 4KiB of data in the new LV. Default is y. Snapshot COW\nvolumes are always zeroed. For thin pools, this controls zeroing of provisioned\nblocks. LV is not zeroed if the read only flag is set. Warning: trying to mount an\nunzeroed LV can cause the system to hang.\n", "flag": "-Z", "long": "--zero" } ] }, "VARIABLES": { "content": "VG Volume Group name. See lvm(8) for valid names. For lvcreate, the required VG posi‐\ntional arg may be omitted when the VG name is included in another option, e.g. --name\nVG/LV.\n\nLV Logical Volume name. See lvm(8) for valid names. An LV positional arg generally in‐\ncludes the VG name and LV name, e.g. VG/LV. LV1 indicates the LV must have a specific\ntype, where the accepted LV types are listed. (raid represents raid type).\n\nPV Physical Volume name, a device path under /dev. For commands managing physical ex‐\ntents, a PV positional arg generally accepts a suffix indicating a range (or multiple\nranges) of physical extents (PEs). When the first PE is omitted, it defaults to the\nstart of the device, and when the last PE is omitted it defaults to end. Start and\nend range (inclusive): PV[:PE-PE]... Start and length range (counting from 0):\nPV[:PE+PE]...\n\nString See the option description for information about the string content.\n\nSize[UNIT]\nSize is an input number that accepts an optional unit. Input units are always treated\nas base two values, regardless of capitalization, e.g. 'k' and 'K' both refer to 1024.\nThe default input unit is specified by letter, followed by |UNIT. UNIT represents\nother possible input units: b|B is bytes, s|S is sectors of 512 bytes, k|K is KiB, m|M\nis MiB, g|G is GiB, t|T is TiB, p|P is PiB, e|E is EiB. (This should not be confused\nwith the output control --units, where capital letters mean multiple of 1000.)\n", "subsections": [] }, "ENVIRONMENT VARIABLES": { "content": "See lvm(8) for information about environment variables used by lvm. For example, LVMVGNAME\ncan generally be substituted for a required VG parameter.\n", "subsections": [] }, "ADVANCED USAGE": { "content": "Alternate command forms, advanced command usage, and listing of all valid syntax for com‐\npleteness.\n\nCreate an LV that returns errors when used.\n\nlvcreate --type error -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ COMMONOPTIONS ]\n\n—\n\nCreate an LV that returns zeros when read.\n\nlvcreate --type zero -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ COMMONOPTIONS ]\n\n—\n\nCreate a linear LV.\n\nlvcreate --type linear -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a striped LV (also see lvcreate --stripes).\n\nlvcreate --type striped -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a mirror LV (also see --type raid1).\n\nlvcreate --type mirror -L|--size Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -m|--mirrors Number ]\n[ -R|--regionsize Size[m|UNIT] ]\n[ --mirrorlog core|disk ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a COW snapshot LV of an origin LV\n(also see --snapshot).\n\nlvcreate --type snapshot -L|--size Size[m|UNIT] LV\n[ -l|--extents Number[PERCENT] ]\n[ -s|--snapshot ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a sparse COW snapshot LV of a virtual origin LV\n(also see --snapshot).\n\nlvcreate --type snapshot -L|--size Size[m|UNIT]\n-V|--virtualsize Size[m|UNIT] VG\n[ -l|--extents Number[PERCENT] ]\n[ -s|--snapshot ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin pool.\n\nlvcreate -T|--thin -L|--size Size[m|UNIT] VG\n[ --type thin-pool ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin pool named in --thinpool.\n\nlvcreate -L|--size Size[m|UNIT] --thinpool LVnew VG\n[ --type thin-pool ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a cache pool named by the --cachepool arg\n(variant, uses --cachepool in place of --name).\n\nlvcreate --type cache-pool -L|--size Size[m|UNIT]\n--cachepool LVnew VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -H|--cache ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV in a thin pool.\n\nlvcreate --type thin -V|--virtualsize Size[m|UNIT]\n--thinpool LV VG\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\n—\n\nCreate a thin LV in a thin pool named in the first arg\n(variant, also see --thinpool for naming pool).\n\nlvcreate --type thin -V|--virtualsize Size[m|UNIT] LV1\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\nLV1 types: thinpool\n\n—\n\nCreate a thin LV in the thin pool named in the first arg\n(also see --thinpool for naming pool.)\n\nlvcreate -V|--virtualsize Size[m|UNIT] LV1\n[ --type thin ] (implied)\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\nLV1 types: thinpool\n\n—\n\nCreate a thin LV that is a snapshot of an existing thin LV.\n\nlvcreate --type thin LV1\n[ -T|--thin ]\n[ COMMONOPTIONS ]\n\nLV1 types: thin\n\n—\n\nCreate a thin LV that is a snapshot of an existing thin LV.\n\nlvcreate -T|--thin LV1\n[ --type thin ] (implied)\n[ COMMONOPTIONS ]\n\nLV1 types: thin\n\n—\n\nCreate a thin LV that is a snapshot of an external origin LV.\n\nlvcreate -s|--snapshot --thinpool LV LV\n[ --type thin ] (implied)\n[ COMMONOPTIONS ]\n\n—\n\nCreate a VDO LV with VDO pool.\n\nlvcreate --vdo -L|--size Size[m|UNIT] VG\n[ --type vdo ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -V|--virtualsize Size[m|UNIT] ]\n[ --vdopool LVnew ]\n[ --compression y|n ]\n[ --deduplication y|n ]\n[ --vdosettings String ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a VDO LV with VDO pool.\n\nlvcreate --vdopool LVnew -L|--size Size[m|UNIT] VG\n[ --type vdo ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -V|--virtualsize Size[m|UNIT] ]\n[ --compression y|n ]\n[ --deduplication y|n ]\n[ --vdosettings String ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV, first creating a thin pool for it,\nwhere the new thin pool is named by the --thinpool arg.\n\nlvcreate --type thin -V|--virtualsize Size[m|UNIT]\n-L|--size Size[m|UNIT] --thinpool LVnew VG\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV, first creating a thin pool for it,\nwhere the new thin pool is named by --thinpool.\n\nlvcreate -V|--virtualsize Size[m|UNIT] -L|--size Size[m|UNIT]\n--thinpool LVnew VG\n[ --type thin ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV, first creating a thin pool for it,\nwhere the new thin pool is named in the first arg,\nor the new thin pool name is generated when the first\narg is a VG name.\n\nlvcreate --type thin -V|--virtualsize Size[m|UNIT]\n-L|--size Size[m|UNIT] VG|LVnew\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV, first creating a thin pool for it,\nwhere the new thin pool is named in the first arg,\nor the new thin pool name is generated when the first\narg is a VG name.\n\nlvcreate -T|--thin -V|--virtualsize Size[m|UNIT]\n-L|--size Size[m|UNIT] VG|LVnew\n[ --type thin ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a thin LV, first creating a thin pool for it.\nCreate a sparse snapshot of a virtual origin LV\nChooses type thin or snapshot according to\nconfig setting sparsesegtypedefault.\n\nlvcreate -L|--size Size[m|UNIT] -V|--virtualsize Size[m|UNIT] VG\n[ --type thin|snapshot ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -s|--snapshot ]\n[ -T|--thin ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --discards passdown|nopassdown|ignore ]\n[ --errorwhenfull y|n ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach the specified cachepool\nwhich converts the new LV to type cache.\n\nlvcreate -L|--size Size[m|UNIT] --cachepool LV VG\n[ --type cache ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -H|--cache ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n\nCreate a new LV, then attach the specified cachepool\nwhich converts the new LV to type cache.\n(variant, also use --cachepool).\n\nlvcreate --type cache -L|--size Size[m|UNIT] LV1\n[ -l|--extents Number[PERCENT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ -H|--cache ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\nLV1 types: cachepool\n\n—\n\nWhen the LV arg is a cachepool, then create a new LV and\nattach the cachepool arg to it.\n(variant, use --type cache and --cachepool.)\nWhen the LV arg is not a cachepool, then create a new cachepool\nand attach it to the LV arg (alternative, use lvconvert.)\n\nlvcreate -H|--cache -L|--size Size[m|UNIT] LV\n[ --type cache ] (implied)\n[ -l|--extents Number[PERCENT] ]\n[ -c|--chunksize Size[k|UNIT] ]\n[ -i|--stripes Number ]\n[ -I|--stripesize Size[k|UNIT] ]\n[ --cachemode writethrough|writeback|passthrough ]\n[ --cachepolicy String ]\n[ --cachesettings String ]\n[ --cachemetadataformat auto|1|2 ]\n[ --poolmetadatasize Size[m|UNIT] ]\n[ --poolmetadataspare y|n ]\n[ COMMONOPTIONS ]\n[ PV ... ]\n\n—\n", "subsections": [] }, "EXAMPLES": { "content": "Create a striped LV with 3 stripes, a stripe size of 8KiB and a size of 100MiB. The LV name\nis chosen by lvcreate.", "subsections": [ { "name": "lvcreate -i 3 -I 8 -L 100m vg00", "content": "Create a raid1 LV with two images, and a useable size of 500 MiB. This operation requires two\ndevices, one for each mirror image. RAID metadata (superblock and bitmap) is also included on\nthe two devices." }, { "name": "lvcreate --type raid1 -m1 -L 500m -n mylv vg00", "content": "Create a mirror LV with two images, and a useable size of 500 MiB. This operation requires\nthree devices: two for mirror images and one for a disk log." }, { "name": "lvcreate --type mirror -m1 -L 500m -n mylv vg00", "content": "Create a mirror LV with 2 images, and a useable size of 500 MiB. This operation requires 2\ndevices because the log is in memory." }, { "name": "lvcreate --type mirror -m1 --mirrorlog core -L 500m -n mylv vg00", "content": "Create a copy-on-write snapshot of an LV:" }, { "name": "lvcreate --snapshot --size 100m --name mysnap vg00/mylv", "content": "Create a copy-on-write snapshot with a size sufficient for overwriting 20% of the size of the\noriginal LV." }, { "name": "lvcreate -s -l 20%ORIGIN -n mysnap vg00/mylv", "content": "Create a sparse LV with 1TiB of virtual space, and actual space just under 100MiB." }, { "name": "lvcreate --snapshot --virtualsize 1t --size 100m --name mylv vg00", "content": "Create a linear LV with a usable size of 64MiB on specific physical extents." }, { "name": "lvcreate -L 64m -n mylv vg00 /dev/sda:0-7 /dev/sdb:0-7", "content": "Create a RAID5 LV with a usable size of 5GiB, 3 stripes, a stripe size of 64KiB, using a to‐\ntal of 4 devices (including one for parity)." }, { "name": "lvcreate --type raid5 -L 5G -i 3 -I 64 -n mylv vg00", "content": "Create a RAID5 LV using all of the free space in the VG and spanning all the PVs in the VG\n(note that the command will fail if there are more than 8 PVs in the VG, in which case -i 7\nmust be used to get to the current maximum of 8 devices including parity for RaidLVs)." }, { "name": "lvcreate --config allocation/raid_stripe_all_devices=1", "content": "--type raid5 -l 100%FREE -n mylv vg00\n\nCreate RAID10 LV with a usable size of 5GiB, using 2 stripes, each on a two-image mirror.\n(Note that the -i and -m arguments behave differently: -i specifies the total number of\nstripes, but -m specifies the number of images in addition to the first image)." }, { "name": "lvcreate --type raid10 -L 5G -i 2 -m 1 -n mylv vg00", "content": "Create a 1TiB thin LV mythin, with 256GiB thinpool tpool0 in vg00." }, { "name": "lvcreate -T -V 1T --size 256G --name mythin vg00/tpool0", "content": "Create a 1TiB thin LV, first creating a new thin pool for it, where the thin pool has 100MiB\nof space, uses 2 stripes, has a 64KiB stripe size, and 256KiB chunk size." }, { "name": "lvcreate --type thin --name mylv --thinpool mypool", "content": "-V 1t -L 100m -i 2 -I 64 -c 256 vg00\n\nCreate a thin snapshot of a thin LV (the size option must not be used, otherwise a copy-\non-write snapshot would be created)." }, { "name": "lvcreate --snapshot --name mysnap vg00/thinvol", "content": "Create a thin snapshot of the read-only inactive LV named \"origin\" which becomes an external\norigin for the thin snapshot LV." }, { "name": "lvcreate --snapshot --name mysnap --thinpool mypool vg00/origin", "content": "Create a cache pool from a fast physical device. The cache pool can then be used to cache an\nLV." }, { "name": "lvcreate --type cache-pool -L 1G -n my_cpool vg00 /dev/fast1", "content": "Create a cache LV, first creating a new origin LV on a slow physical device, then combining\nthe new origin LV with an existing cache pool." }, { "name": "lvcreate --type cache --cachepool my_cpool", "content": "-L 100G -n mylv vg00 /dev/slow1\n\nCreate a VDO LV vdo0 with VDOPoolLV size of 10GiB and name vpool1." }, { "name": "lvcreate --vdo --size 10G --name vdo0 vg00/vpool1", "content": "" } ] }, "SEE ALSO": { "content": "lvm(8), lvm.conf(5), lvmconfig(8), lvmdevices(8),\n\npvchange(8), pvck(8), pvcreate(8), pvdisplay(8), pvmove(8), pvremove(8), pvresize(8), pvs(8),\npvscan(8),\n\nvgcfgbackup(8), vgcfgrestore(8), vgchange(8), vgck(8), vgcreate(8), vgconvert(8),\nvgdisplay(8), vgexport(8), vgextend(8), vgimport(8), vgimportclone(8), vgimportdevices(8),\nvgmerge(8), vgmknodes(8), vgreduce(8), vgremove(8), vgrename(8), vgs(8), vgscan(8),\nvgsplit(8),\n\nlvcreate(8), lvchange(8), lvconvert(8), lvdisplay(8), lvextend(8), lvreduce(8), lvremove(8),\nlvrename(8), lvresize(8), lvs(8), lvscan(8),\n\nlvm-fullreport(8), lvm-lvpoll(8), blkdeactivate(8), lvmdump(8),\n\ndmeventd(8), lvmpolld(8), lvmlockd(8), lvmlockctl(8), cmirrord(8), lvmdbusd(8), fsadm(8),\n\nlvmsystemid(7), lvmreport(7), lvmraid(7), lvmthin(7), lvmcache(7)\n\nRed Hat, Inc. LVM TOOLS 2.03.16(2) (2022-05-18) LVCREATE(8)", "subsections": [] } } } }