Como estender um volume lógico (LVM) para utilizar a capacidade em um grupo de volume diferente?

Navegue suas respostas
0

Estou executando um servidor Centos 6, que possui 3 volumes físicos. Cada um desses volumes físicos, como um grupo de volumes associado a ele, e cada um desses grupos de volumes, tem um volume lógico associado a ele.

Volumes físicos 

--- Physical volume ---
PV Name               /dev/xvdc
VG Name               vg_applogs
PV Size               80.00 GiB / not usable 4.00 MiB
Allocatable           yes (but full)
PE Size               4.00 MiB
Total PE              20479
Free PE               0
Allocated PE          20479
PV UUID               cy7tNX-QwbJ-4ceZ-XKv1-VwSp-38S4-oLIeNF

--- Physical volume ---
PV Name               /dev/xvdb
VG Name               vg_app
PV Size               35.00 GiB / not usable 4.00 MiB
Allocatable           yes
PE Size               4.00 MiB
Total PE              8959
Free PE               7679
Allocated PE          1280
PV UUID               zbXMCG-Q49f-l1GI-3A7d-AL7m-CwZq-gawtS2

--- Physical volume ---
PV Name               /dev/xvda2
VG Name               VolGroup
PV Size               19.51 GiB / not usable 3.00 MiB
Allocatable           yes (but full)
PE Size               4.00 MiB
Total PE              4994
Free PE               0
Allocated PE          4994
PV UUID               rK3R1r-zw5i-Jk2v-IO3d-nsg8-UpkW-Kbt6Q2

Grupos de volumes 

--- Volume group ---
VG Name               vg_applogs
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No  2
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                1
Open LV               1
Max PV                0
Cur PV                1
Act PV                1
VG Size               80.00 GiB
PE Size               4.00 MiB
Total PE              20479
Alloc PE / Size       20479 / 80.00 GiB
Free  PE / Size       0 / 0
VG UUID               UlMQlU-pG3Y-sSDa-ZWnV-1ZqO-D9vG-3aeQTq

--- Volume group ---
VG Name               vg_app
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No  3
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                1
Open LV               1
Max PV                0
Cur PV                1
Act PV                1
VG Size               35.00 GiB
PE Size               4.00 MiB
Total PE              8959
Alloc PE / Size       1280 / 5.00 GiB
Free  PE / Size       7679 / 30.00 GiB
VG UUID               Su9Uqv-eim1-bqXR-H5FJ-t0iq-pKq7-DpuAJw

--- Volume group ---
VG Name               VolGroup
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No  3
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                2
Open LV               2
Max PV                0
Cur PV                1
Act PV                1
VG Size               19.51 GiB
PE Size               4.00 MiB
Total PE              4994
Alloc PE / Size       4994 / 19.51 GiB
Free  PE / Size       0 / 0
VG UUID               cUsYpP-nKG3-r18W-rdcv-Cw3u-8eWh-KUfaFm

Volumes lógicos 

--- Logical volume ---
LV Path                /dev/vg_applogs/lv_applogs
LV Name                lv_applogs
VG Name                vg_applogs
LV UUID                rcQVDe-vSMY-eUHy-VSZy-3453-nsCS-L7llXF
LV Write Access        read/write
LV Creation host, time grdvla2100, 2017-05-09 19:34:35 +0100
LV Status              available
# open                 1
LV Size                80.00 GiB
Current LE             20479
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:2

--- Logical volume ---
LV Path                /dev/vg_app/lv_app
LV Name                lv_app
VG Name                vg_app
LV UUID                rwze2a-DdK1-yUAw-JcCO-LStU-0S1m-C7AVKD
LV Write Access        read/write
LV Creation host, time grdvla2100, 2017-05-09 19:24:15 +0100
LV Status              available
# open                 1
LV Size                5.00 GiB
Current LE             1280
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:3

--- Logical volume ---
LV Path                /dev/VolGroup/lv_root
LV Name                lv_root
VG Name                VolGroup
LV UUID                7QbtNM-bob5-KP3H-5GZe-ySuc-2q3c-GPj4DM
LV Write Access        read/write
LV Creation host, time localhost.localdomain, 2017-05-09 17:20:08 +0100
LV Status              available
# open                 1
LV Size                17.51 GiB
Current LE             4482
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:0

Estou procurando usar a capacidade extra disponível em Volume físico / dev / xvdb ( Grupo de volume : vg_app ) e utilizá-lo no Grupo de Volumes vg_applogs à medida que o Volume Lógico lv_applogs é preenchido muito rapidamente.

Qual é a melhor maneira de estender o volume lógico ( lv_applogs ) / grupo de volumes ( vg_applogs ) e usar a capacidade disponível que está disponível no Grupo de Volumes ( vg_app )?

PS: Eu não acho que o / dev / xvdb tenha nenhuma tabela de partições no momento: 

fdisk -l

Disk /dev/xvda: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00094f24

    Device Boot      Start         End      Blocks   Id  System
/dev/xvda1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/xvda2              64        2611    20458496   8e  Linux LVM

Disk /dev/xvdc: 85.9 GB, 85899345920 bytes
255 heads, 63 sectors/track, 10443 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/xvdd: 120 MB, 120254464 bytes
255 heads, 63 sectors/track, 14 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/xvdb: 37.6 GB, 37580963840 bytes
255 heads, 63 sectors/track, 4568 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/VolGroup-lv_root: 18.8 GB, 18798870528 bytes
255 heads, 63 sectors/track, 2285 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/VolGroup-lv_swap: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_applogs-lv_applogs: 85.9 GB, 85895151616 bytes
255 heads, 63 sectors/track, 10442 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_app-lv_app: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
    
por user3637413 12.12.2017 / 15:14

1 resposta

2

Em suma, você não pode. LVs devem estar contidos inteiramente dentro de um único VG, você não pode ter um LV ocupando espaço em múltiplos VGs.

    
por 12.12.2017 / 15:22

Tags

udev systemd chamada @remove não funciona, mas aciona scripts openSuse Leap42.3 Como baixar o endereço de email que se referiu dentro da página web com o wget? [fechadas]