lvmdevices

List devices recorded in the devices file

$ sudo lvmdevices

$ sudo lvmdevices --adddev [/dev/sdXN]

$ sudo lvmdevices --deldev [/dev/sdXN]

$ sudo lvmdevices --addpvid [PVID]

$ sudo lvmdevices --delpvid [PVID]

$ sudo lvmdevices --update

$ sudo lvmdevices --check

$ lvmdevices --version

N/A: 'lvmdevices' is not a directly executable command.

The term 'lvmdevices' does not correspond to a standard, directly executable Linux command within the Logical Volume Manager (LVM) framework. It is likely a conceptual reference to the methods and components LVM uses to manage storage devices. LVM handles physical storage (hard drives, partitions) by organizing them into a hierarchy of Physical Volumes (PVs), Volume Groups (VGs), and Logical Volumes (LVs).

Each of these stages, from initializing a raw device as a PV to creating and managing an LV, is performed using a specific set of LVM utilities (e.g., pvcreate, vgcreate, lvcreate, pvdisplay, vgdisplay, lvdisplay, etc.). There is no single, unified command named 'lvmdevices' that encompasses all these individual operations. Users seeking to interact with or configure LVM devices should refer to the specific commands dedicated to each LVM component.

Attempting to execute lvmdevices directly in a shell will result in a 'command not found' error, as it is not an actual executable. All LVM device-related operations must be performed using the specific, well-defined LVM commands like pvcreate, vgcreate, lvcreate, and their various management counterparts. Misunderstanding this can lead to confusion or incorrect system administration practices.

LVM structures storage into a distinct hierarchy to provide flexibility and abstraction over physical storage:

• Physical Volumes (PVs): These are the base components, typically raw disk partitions or whole disks, initialized using pvcreate. They serve as the raw storage units for LVM.
• Volume Groups (VGs): A VG is formed by combining one or more PVs using vgcreate. It acts as a pool of storage from which logical volumes are allocated.
• Logical Volumes (LVs): These are the user-facing 'disks' created within a VG using lvcreate. LVs can be resized, snapshotted, and mirrored independently of the underlying physical storage, providing flexibility.
  Each step of this hierarchy is managed by its own set of dedicated LVM commands.

Since the inception of LVM, the design philosophy has been to provide a modular set of tools for each specific aspect of logical volume management, rather than a monolithic command. Therefore, a standalone 'lvmdevices' command has never been part of the official LVM toolset. This approach allows for granular control and clear separation of concerns in managing physical volumes, volume groups, and logical volumes. The evolution of LVM (from LVM1 to LVM2) has refined these individual commands but has not introduced a singular 'lvmdevices' utility.

lvm(8), lvm.conf(5), pvcreate(8), vgcreate(8), lvcreate(8), pvs(8), vgs(8), lvs(8), pvdisplay(8), vgdisplay(8), lvdisplay(8)