hi,
i've read here
http://docs.redhat.com/docs/en-US/R...uster_Logical_Volume_Manager/VG_activate.html
about activating or deactivating volume groups, and it says <<When you create a volume group it is, by default, activated. This means that the logical volumes in that group are accessible and subject to change. There are various circumstances for which you you need to make a volume group inactive and thus unknown to the kernel.>>
i thought that activated or deactivated had something to do with the vm being on or off, but i was digging in my lvs with lvdisplay and found, for two "off" vm, 206 and 209:
how should they be and why?
lvdisplay /dev/pve_vm_disks/vm-206-disk-1
--- Logical volume ---
LV Path /dev/pve_vm_disks/vm-206-disk-1
LV Name vm-206-disk-1
VG Name pve_vm_disks
LV UUID H7Klcj-AoM3-dAEB-xImj-AP1x-Ijp1-P2HTXy
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 5.01 GiB
Current LE 1283
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:34
root@pve2:~# lvdisplay /dev/pve_vm_disks/vm-209-disk-1
--- Logical volume ---
LV Path /dev/pve_vm_disks/vm-209-disk-1
LV Name vm-209-disk-1
VG Name pve_vm_disks
LV UUID ugnIe3-MqL9-Xgdb-JP4o-9JSU-c0T0-zEwFfS
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 42.01 GiB
Current LE 10754
Segments 2
Allocation inherit
Read ahead sectors auto
Thanks, Marco
i've read here
http://docs.redhat.com/docs/en-US/R...uster_Logical_Volume_Manager/VG_activate.html
about activating or deactivating volume groups, and it says <<When you create a volume group it is, by default, activated. This means that the logical volumes in that group are accessible and subject to change. There are various circumstances for which you you need to make a volume group inactive and thus unknown to the kernel.>>
i thought that activated or deactivated had something to do with the vm being on or off, but i was digging in my lvs with lvdisplay and found, for two "off" vm, 206 and 209:
how should they be and why?
lvdisplay /dev/pve_vm_disks/vm-206-disk-1
--- Logical volume ---
LV Path /dev/pve_vm_disks/vm-206-disk-1
LV Name vm-206-disk-1
VG Name pve_vm_disks
LV UUID H7Klcj-AoM3-dAEB-xImj-AP1x-Ijp1-P2HTXy
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 5.01 GiB
Current LE 1283
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:34
root@pve2:~# lvdisplay /dev/pve_vm_disks/vm-209-disk-1
--- Logical volume ---
LV Path /dev/pve_vm_disks/vm-209-disk-1
LV Name vm-209-disk-1
VG Name pve_vm_disks
LV UUID ugnIe3-MqL9-Xgdb-JP4o-9JSU-c0T0-zEwFfS
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 42.01 GiB
Current LE 10754
Segments 2
Allocation inherit
Read ahead sectors auto
Thanks, Marco
Last edited: