Linux Red hat 7 & Python - Como mapear uma unidade LVM2 com o mesmo name?

Droni
(usa Red Hat)

Enviado em 08/04/2020 - 12:37h

Prezados, boa tarde !!!!!!!!!!!!!!!!

Socorro rsrs

Estou desenvolvendo uma automação onde irei ler um disco anexado a minha instancia para que eu faça o mapeamento, copie os dados e depois encerro o mapeamento, contudo, esta unidade é um snapshot de outra maquina, no formato LVM2, até ai tudo bem, vou criar uma automação para fazer o MOUNT desta unidade LVM2, contudo, veja como está esta unidade, ela está com o VG NAME igual e LV NAME igual !! Como faço para mapear neste caso?

Nao precisa ser especificamente em Python, se for o caso, posso usar o "os.system" para rodar um comando em shell script por exemplo ou simplesmente linhas de comando do terminal, me ajudem por favor! Obrigado !!!!!!

OBS: No caso, quero mapear a unidade cujo status está como "NOT AVALIABLE":

[root@110725-core_instance-N_PR_D_CSALVA-1-4fcb4652a4LIN protheus_data_prod]# lvdisplay
File descriptor 63 (pipe:[31378751]) leaked on lvdisplay invocation. Parent PID 13091: bash
--- Logical volume ---
LV Path /dev/vg00_outsourcing/lv_protheus
LV Name lv_protheus
VG Name vg00_outsourcing
LV UUID zEt4qU-mP6n-U4D8-1xKW-Ogq2-HizB-0D1Mio
LV Write Access read/write
LV Creation host, time 110725-core_instance-N_PR_D_CSALVA-1-4fcb4652a4LIN, 2020-02-06 19:19:20 -0300
LV Status available
# open 1
LV Size <75.00 GiB
Current LE 19199
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 252:0

--- Logical volume ---
LV Path /dev/vg00_outsourcing/lv_protheus
LV Name lv_protheus
VG Name vg00_outsourcing
LV UUID lur0Vo-NLIN-66b3-m4je-3PWG-UbQz-XmHwU9
LV Write Access read/write
LV Creation host, time 111400-core_instance-N_PR_P_CSALVA-1-d5bd9ce334LIN, 2020-03-20 10:20:07 -0300
LV Status NOT available
LV Size <75.00 GiB
Current LE 19199
Segments 1
Allocation inherit
Read ahead sectors auto

Droni
(usa Red Hat)

Enviado em 08/04/2020 - 13:44h

Prezados, consegui resolver, e vou compartilhar com vcs!

1 - vgdisplay (coletei o VG_UUID)

[root@110725-core_instance-N_PR_D_CSALVA-1-4fcb4652a4LIN cloud-user]# vgdisplay

File descriptor 63 (pipe:[31397253]) leaked on vgdisplay invocation. Parent PID 21660: bash
--- Volume group ---
VG Name vg00_outsourcing
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 <75.00 GiB
PE Size 4.00 MiB
Total PE 19199
Alloc PE / Size 19199 / <75.00 GiB
Free PE / Size 0 / 0
VG UUID A33WKg-nN7b-5VM7-adlM-2tgw-dtDe-fjOJwv

--- Volume group ---
VG Name vg00_outsourcing
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 0
Max PV 0
Cur PV 1
Act PV 1
VG Size <75.00 GiB
PE Size 4.00 MiB
Total PE 19199
Alloc PE / Size 19199 / <75.00 GiB
Free PE / Size 0 / 0
VG UUID Jt8BN4-T87y-x5Sf-x6Fl-RNuT-jJIp-WiP1fU

2 - Executei o comando de rename:

[root@110725-core_instance-N_PR_D_CSALVA-1-4fcb4652a4LIN cloud-user]# vgrename Jt8BN4-T87y-x5Sf-x6Fl-RNuT-jJIp-WiP1fU vg01_outsourcing

File descriptor 63 (pipe:[31397470]) leaked on vgrename invocation. Parent PID 21660: bash
Processing VG vg00_outsourcing because of matching UUID Jt8BN4-T87y-x5Sf-x6Fl-RNuT-jJIp-WiP1fU
Volume group "Jt8BN4-T87y-x5Sf-x6Fl-RNuT-jJIp-WiP1fU" successfully renamed to "vg01_outsourcing"

3 - Rodei o comando de "commit":

[root@110725-core_instance-N_PR_D_CSALVA-1-4fcb4652a4LIN cloud-user]# vgchange -ay
File descriptor 63 (pipe:[31398056]) leaked on vgchange invocation. Parent PID 21660: bash
1 logical volume(s) in volume group "vg00_outsourcing" now active
1 logical volume(s) in volume group "vg01_outsourcing" now active

4 - Fiz o mount:

mount /dev/mapper/vg01_outsourcing-lv_protheus /outsourcing/totvs/protheus_data_prod

Listou os arquivos \o/

Dps que eu terminar a copia, faço o "umount /outsourcing/totvs/protheus_data_prod e elimino o disco.

Obrigado a todos ai !! Abs!!