LVRENAME(8)
π LVRENAME(8) π β the glow-up page for renaming your LVs
okay bestie, welcome to LVRENAME(8) from the System Manager's Manual. This is the manual page for the lvrename command, and yes, it's from the LVM tools, and yes, we're gonna make it make sense. π
β¨ NAME β¨
lvrename β rename a logical volume. that's it. that's the whole job. iconic behavior honestly. π
πΈ SYNOPSIS πΈ
lvrename position_args
[ option_args ]
π¦ DESCRIPTION π¦
lvrename renames an existing LV, or a historical LV. (if you're sitting there like "girl what is a historical LV", go read lvremove(8) β it explains historical LV info. iykyk π«Ά)
π USAGE π
here's the tea, there are two ways to say it:
lvrename VG LV LV_new
[ COMMON_OPTIONS ]
β
lvrename LV LV_new
[ COMMON_OPTIONS ]
β
Common options for command:
[ -A|--autobackup y|n ]
[ --noudevsync ]
[ --reportformat basic|json|json_std ]
Common options for lvm:
[ -d|--debug ... ]
[ -h|--help ]
[ -q|--quiet ... ]
[ -t|--test ]
[ -v|--verbose ... ]
[ -y|--yes ]
[ --commandprofile String ]
[ --config String ]
[ --devices PV ]
[ --devicesfile String ]
[ --driverloaded y|n ]
[ --journal String ]
[ --lockopt String ]
[ --longhelp ]
[ --nohints ]
[ --nolocking ]
[ --profile String ]
[ --version ]
π₯ OPTIONS π₯
-A,--autobackup y|nβ says whether metadata should be automatically backed up after a change. turning this ON is strongly advised!! like, please. go readvgcfgbackup(8)for the full picture. π--commandprofile Stringβ the command profile you wanna use for command configuration. checklvm.conf(5)for more about profiles. β¨--config Stringβ config settings for the command. these override thelvm.conf(5)settings. theStringarg uses the same format aslvm.conf(5), or it can usesection/fieldsyntax. more info about config lives inlvm.conf(5). π-d,--debug ...β set the debug level. repeat it from 1 to 6 times to increase how much detail goes into the log file and/or syslog (if it's configured). π--devices PVβ restricts which devices are visible and accessible to the command. devices that aren't listed will appear to be missing π (they're not gone, they're just shadowbanned). this option can be repeated, or it accepts a comma-separated 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 thelvmdevices(8)command. this overrides thelvm.conf(5)devices/devicesfileanddevices/use_devicesfilesettings. πΈ--driverloaded y|nβ if you set it to no, the command won't even attempt to use device-mapper. for testing and debugging only, bestie. π§ͺ-h,--helpβ display help text. the classic. π«Ά--journal Stringβ record info in the systemd journal. this is in addition to whatever info thelvm.conflog/journalsetting already enables. the options are:command:for info about the command,output:for the default command output, anddebug:for full command debugging. β--lockopt Stringβ used to pass options for special cases tolvmlockd. seelvmlockd(8)for more. π--longhelpβ display long help text. the extended cut. π--nohintsβ do not use the hints file to locate devices for PVs. a command may read more devices to find PVs when hints aren't used. the command will still do standard hint file invalidation where it's appropriate, so don't stress. π--nolockingβ disable locking. use with caution: concurrent commands may produce incorrect results. π--noudevsyncβ disables udev synchronization. the process won't wait for a notification from udev, and it'll keep going no matter what udev processing might be happening in the background. only use this if udev isn't running, or if it has rules that ignore the devices LVM creates. π--profile Stringβ an alias for--commandprofileor--metadataprofile, depending on the command. π-q,--quiet ...β suppress output and log messages. this overrides--debugand--verbose. repeat it once to also suppress any prompts with the answer 'no'. silence truly is golden. π€«--reportformat basic|json|json_stdβ overrides the current output format for reports, which is defined globally by thereport/output_formatsetting inlvm.conf(5).basicis the original format with columns and rows β if there's more than one report per command, each report gets prefixed with the report name so you can tell them apart.jsonproduces report output in JSON format.json_stdproduces report output in JSON format that's more compliant with the JSON standard. seelvmreport(7)for more. π-t,--testβ run in test mode. commands will not update metadata. this works by disabling all metadata writing but still returning success to the calling function π which means you might get unusual error messages in multi-stage operations if a tool relies on reading back metadata it thinks has changed but actually hasn't. sneaky. π-v,--verbose ...β set the verbose level. repeat it from 1 to 4 times to increase how much detail gets sent to stdout and stderr. π£οΈ--versionβ display version information. β¨-y,--yesβ don't prompt for confirmation interactively, just always assume the answer is yes. use with extreme caution. (for an automatic no, see-qq.) π₯
π VARIABLES π
VGβ Volume Group name. seelvm(8)for valid names. πLVβ Logical Volume name. seelvm(8)for valid names. anLVpositional arg generally includes both the VG name and the LV name, likeVG/LV. πΈStringβ see the option description for info about what the string should contain. π¦Size[UNIT]βSizeis an input number that accepts an optional unit. input units are always treated as base two values, no matter the capitalization β so'k'and'K'both refer to 1024. the default input unit is specified by letter, followed by|UNIT.UNITrepresents the other possible input units:b|Bis bytes,s|Sis sectors of 512 bytes,k|Kis KiB,m|Mis MiB,g|Gis GiB,t|Tis TiB,p|Pis PiB,e|Eis EiB. (and do NOT confuse this with the output control--units, where capital letters mean multiple of 1000. different vibe entirely.)
π ENVIRONMENT VARIABLES π
see lvm(8) for info about environment variables used by lvm. for example, LVM_VG_NAME can generally be substituted for a required VG parameter. so convenient. π
β EXAMPLES β
rename "lvold" to "lvnew":
lvrename /dev/vg02/lvold vg02/lvnew
an alternate syntax to rename "lvold" to "lvnew":
lvrename vg02 lvold lvnew
π SEE ALSO π
lvm(8), lvm.conf(5), lvmconfig(8), lvmdevices(8),
pvchange(8), pvck(8), pvcreate(8), pvdisplay(8), pvmove(8), pvremove(8), pvresize(8), pvs(8), pvscan(8),
vgcfgbackup(8), vgcfgrestore(8), vgchange(8), vgck(8), vgcreate(8), vgconvert(8), vgdisplay(8), vgexport(8), vgextend(8), vgimport(8), vgimportclone(8), vgimportdevices(8), vgmerge(8), vgmknodes(8), vgreduce(8), vgremove(8), vgrename(8), vgs(8), vgscan(8), vgsplit(8),
lvcreate(8), lvchange(8), lvconvert(8), lvdisplay(8), lvextend(8), lvreduce(8), lvremove(8), lvrename(8), lvresize(8), lvs(8), lvscan(8),
lvm-fullreport(8), lvm-lvpoll(8), blkdeactivate(8), lvmdump(8),
dmeventd(8), lvmpolld(8), lvmlockd(8), lvmlockctl(8), lvmdbusd(8), fsadm(8),
lvmsystemid(7), lvmreport(7), lvmcache(7), lvmraid(7), lvmthin(7), lvmvdo(7), lvmautoactivation(7)
okay that's the whole page bestie, you're officially lvrename-pilled π this masterpiece is brought to you by Red Hat, Inc., running LVM TOOLS 2.03.44(2), dated 2026-10-27. go forth and rename responsibly π«Άβ¨
π¦ where this page comes from
- arch rolling: lvm2 2.03.44-1 Β· GPL-2.0-only AND LGPL-2.1-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms