Атрибуты состояния физических томов:
# pvs PV VG Fmt Attr PSize PFree /dev/md1 vg0 lvm2 a-- 930,45g 38,11g
1 bit — (a)llocatable
2 bit — e(x)ported
3 bit — (m)issing
Атрибуты состояния групп томов:
# vgs VG #PV #LV #SN Attr VSize VFree cluster 1 2 0 wz--n- 931.48g 731.48g pve 1 3 0 wz--n- 931.38g 16.00g
1 bit — Permissions: (w)riteable, (r)ead-only
2 bit — Resi(z)eable
3 bit — E(x)ported
4 bit — (p)artial: one or more physical volumes belonging to the volume group are missing from the system
5 bit — Allocation policy: (c)ontiguous, c(l)ing, (n)ormal, (a)nywhere, (i)nherited
6 bit — (c)lustered
Атрибуты состояния логический точеских томов:
# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert vm-100-disk-1 cluster -wi-ao--- 100.00g vm-102-disk-1 cluster -wi-ao--- 100.00g data pve -wi-ao--- 847.39g root pve -wi-ao--- 60.00g swap pve -wi-ao--- 8.00g
1 bit — Volume type: (m)irrored, (M)irrored without initial sync, (o)rigin, (O)rigin with merging snapshot, (r)aid, (R)aid without initial sync, (s)napshot, merging (S)napshot, (p)vmove, (v)irtual, mirror or raid (i)mage, mirror or raid (I)mage out-of-sync, mirror (l)og device, under (c)onversion, thin (V)olume, (t)hin pool, (T)hin pool data, raid or thin pool m(e)tadata
2 bit — Permissions: (w)riteable, (r)ead-only, (R)ead-only activation of non-read-only volume
3 bit — Allocation policy: (a)nywhere, (c)ontiguous, (i)nherited, c(l)ing, (n)ormal. This is capitalised if the volume is currently locked against allocation changes, for example during pvmove(8).
4 bit — fixed (m)inor
5 bit — State: (a)ctive, (s)uspended, (I)nvalid snapshot, invalid (S)uspended snapshot, snapshot (m)erge failed, suspended snapshot (M)erge failed, mapped (d)evice present without tables, mapped device present with (i)nactive table
6 bit — device (o)pen
7 bit — Target type: (m)irror, (r)aid, (s)napshot, (t)hin, (u)nknown, (v)irtual. This groups logical volumes related to the same kernel target together. So, for example, mirror images, mirror logs as well as mirrors themselves appear as (m) if they use the original device-mapper mirror kernel driver; whereas the raid equivalents using the md raid kernel driver all appear as (r). Snapshots using the original device-mapper driver appear as (s); whereas snapshots of thin volumes using the new thin provisioning driver appear as (t).
8 bit — Newly-allocated data blocks are overwritten with blocks of (z)eroes before use.
9 bit — (p)artial: One or more of the Physical Volumes this Logical Volume uses is missing from the system.