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 read vgcfgbackup(8) for the full picture. πŸ’–
  • --commandprofile String β€” the command profile you wanna use for command configuration. check lvm.conf(5) for more about profiles. ✨
  • --config String β€” config settings for the command. these override the lvm.conf(5) settings. the String arg uses the same format as lvm.conf(5), or it can use section/field syntax. more info about config lives in lvm.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 the lvmdevices(8) command. this overrides the lvm.conf(5) devices/devicesfile and devices/use_devicesfile settings. 🌸
  • --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 the lvm.conf log/journal setting already enables. the options are: command: for info about the command, output: for the default command output, and debug: for full command debugging. ⭐
  • --lockopt String β€” used to pass options for special cases to lvmlockd. see lvmlockd(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 --commandprofile or --metadataprofile, depending on the command. πŸ’…
  • -q, --quiet ... β€” suppress output and log messages. this overrides --debug and --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 the report/output_format setting in lvm.conf(5). basic is 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. json produces report output in JSON format. json_std produces report output in JSON format that's more compliant with the JSON standard. see lvmreport(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. see lvm(8) for valid names. πŸ’œ
  • LV β€” Logical Volume name. see lvm(8) for valid names. an LV positional arg generally includes both the VG name and the LV name, like VG/LV. 🌸
  • String β€” see the option description for info about what the string should contain. πŸ¦‹
  • Size[UNIT] β€” Size is 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. UNIT represents the other possible input units: b|B is bytes, s|S is sectors of 512 bytes, k|K is KiB, m|M is MiB, g|G is GiB, t|T is TiB, p|P is PiB, e|E is 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