mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-04-28 04:35:36 +00:00
28eb02fb33
Update the examples to use the newer `pvesm scan` subcommands instead of their backwards compatibility aliases to encourage new users to use the new subcommand. Signed-off-by: Daniel Kral <d.kral@proxmox.com> Link: https://lore.proxmox.com/20250304100915.55114-2-d.kral@proxmox.com
91 lines
2.1 KiB
Plaintext
91 lines
2.1 KiB
Plaintext
[[storage_lvmthin]]
|
|
LVM thin Backend
|
|
----------------
|
|
ifdef::wiki[]
|
|
:pve-toplevel:
|
|
:title: Storage: LVM Thin
|
|
endif::wiki[]
|
|
|
|
Storage pool type: `lvmthin`
|
|
|
|
LVM normally allocates blocks when you create a volume. LVM thin pools
|
|
instead allocates blocks when they are written. This behaviour is
|
|
called thin-provisioning, because volumes can be much larger than
|
|
physically available space.
|
|
|
|
You can use the normal LVM command-line tools to manage and create LVM
|
|
thin pools (see `man lvmthin` for details). Assuming you already have
|
|
a LVM volume group called `pve`, the following commands create a new
|
|
LVM thin pool (size 100G) called `data`:
|
|
|
|
----
|
|
lvcreate -L 100G -n data pve
|
|
lvconvert --type thin-pool pve/data
|
|
----
|
|
|
|
|
|
Configuration
|
|
~~~~~~~~~~~~~
|
|
|
|
The LVM thin backend supports the common storage properties `content`, `nodes`,
|
|
`disable`, and the following LVM specific properties:
|
|
|
|
`vgname`::
|
|
|
|
LVM volume group name. This must point to an existing volume group.
|
|
|
|
`thinpool`::
|
|
|
|
The name of the LVM thin pool.
|
|
|
|
|
|
.Configuration Example (`/etc/pve/storage.cfg`)
|
|
----
|
|
lvmthin: local-lvm
|
|
thinpool data
|
|
vgname pve
|
|
content rootdir,images
|
|
----
|
|
|
|
|
|
File naming conventions
|
|
~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
The backend use basically the same naming conventions as the ZFS pool
|
|
backend.
|
|
|
|
vm-<VMID>-<NAME> // normal VM images
|
|
|
|
|
|
Storage Features
|
|
~~~~~~~~~~~~~~~~
|
|
|
|
LVM thin is a block storage, but fully supports snapshots and clones
|
|
efficiently. New volumes are automatically initialized with zero.
|
|
|
|
It must be mentioned that LVM thin pools cannot be shared across
|
|
multiple nodes, so you can only use them as local storage.
|
|
|
|
.Storage features for backend `lvmthin`
|
|
[width="100%",cols="m,m,3*d",options="header"]
|
|
|==============================================================================
|
|
|Content types |Image formats |Shared |Snapshots |Clones
|
|
|images rootdir |raw |no |yes |yes
|
|
|==============================================================================
|
|
|
|
Examples
|
|
~~~~~~~~
|
|
|
|
You can get a list of available LVM thin pools on the volume group `pve` with:
|
|
|
|
# pvesm scan lvmthin pve
|
|
|
|
ifdef::wiki[]
|
|
|
|
See Also
|
|
~~~~~~~~
|
|
|
|
* link:/wiki/Storage[Storage]
|
|
|
|
endif::wiki[]
|