Issue with LVM local storage: Found duplicate PV

J

jcb26

New Member
Oct 23, 2014
6
0
1
Hello,

I have a proxmox 3.3 cluster, with local LVM storage.
I have a Vm (KVM) which run a SLES 11 64 bits. This Vm use internal lvm2 config.

For test purpose, i have restored a backup of that Vm on the same node where the original Vm runs.
The original Vm had number 100, and the new had number 110.

After restore, at the end of the log, i have founded the following message:

Found duplicate PV n0oZ93MQU1LSwD4anAxDMJWSJ2U09PWv: using /dev/dataproxmox-01/vm-110-disk-2 not /dev/dataproxmox-01/vm-100-disk-2
Found duplicate PV SpHywqVzfjpE5IMupAT5yS1uvEddizjo: using /dev/dataproxmox-01/vm-110-disk-3 not /dev/dataproxmox-01/vm-100-disk-3
Found duplicate PV EoUX6oNuA5vcsXcNKtml2uiqGGn1I3CX: using /dev/dataproxmox-01/vm-110-disk-4 not /dev/dataproxmox-01/vm-100-disk-4
Found duplicate PV n0oZ93MQU1LSwD4anAxDMJWSJ2U09PWv: using /dev/dataproxmox-01/vm-110-disk-2 not /dev/dataproxmox-01/vm-100-disk-2
Found duplicate PV SpHywqVzfjpE5IMupAT5yS1uvEddizjo: using /dev/dataproxmox-01/vm-110-disk-3 not /dev/dataproxmox-01/vm-100-disk-3
Found duplicate PV EoUX6oNuA5vcsXcNKtml2uiqGGn1I3CX: using /dev/dataproxmox-01/vm-110-disk-4 not /dev/dataproxmox-01/vm-100-disk-4

So, i have destroyed the new Vm number 110, and i made a pvdisplay and a vgdisplay on the node.

The problem, and it seems not appear with debian, is that Volume groups names and logical volumes names of the Vm appears directly in the node.
In that case: sysvg, datavg, applivg
I have no multipath or bounded devices installed.

The following state is taken after removing Vm number 110. Before removing, number 110 was in place of 100.
Ex: /dev/dataproxmox-01/vm-110-disk-4 against /dev/dataproxmox-01/vm-100-disk-4

Some body have an idea ? Is there something to custom in lvm.conf ?
Please note that i have not this problem with debian wheezy Vms.


--- Physical volume ---
PV Name /dev/sdb1
VG Name dataproxmox-01
PV Size 1.09 TiB / not usable 3.79 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 286069
Free PE 87925
Allocated PE 198144
PV UUID xKCr8C-qqK4-iNL7-yFYW-Ry86-eqI8-k0r457

--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-4
VG Name datavg
PV Size 200.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 51199
Free PE 0
Allocated PE 51199
PV UUID EoUX6o-NuA5-vcsX-cNKt-ml2u-iqGG-n1I3CX

--- Physical volume ---
PV Name /dev/sda3
VG Name pve
PV Size 136.20 GiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 34866
Free PE 4095
Allocated PE 30771
PV UUID L6E9wI-LtEW-Snkj-yFM4-IGnU-8Zn5-fekgsu

--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-3
VG Name applivg
PV Size 20.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 5119
Free PE 0
Allocated PE 5119
PV UUID SpHywq-Vzfj-pE5I-MupA-T5yS-1uvE-ddizjo

--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-2
VG Name sysvg
PV Size 40.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 10239
Free PE 0
Allocated PE 10239
PV UUID n0oZ93-MQU1-LSwD-4anA-xDMJ-WSJ2-U09PWv



--- Volume group ---
VG Name dataproxmox-01
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 56
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 8
Open LV 8
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.09 TiB
PE Size 4.00 MiB
Total PE 286069
Alloc PE / Size 198144 / 774.00 GiB
Free PE / Size 87925 / 343.46 GiB
VG UUID FlNS57-OlYU-MpBR-4P9O-WlKr-tom9-By1cpp


--- Volume group ---
VG Name datavg
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 200.00 GiB
PE Size 4.00 MiB
Total PE 51199
Alloc PE / Size 51199 / 200.00 GiB
Free PE / Size 0 / 0
VG UUID Wxu4gQ-2hmV-Pxk6-dQRX-8M3T-3ha2-iKB9wA

--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 136.20 GiB
PE Size 4.00 MiB
Total PE 34866
Alloc PE / Size 30771 / 120.20 GiB
Free PE / Size 4095 / 16.00 GiB
VG UUID IBh9gN-U9PD-xfg7-aaFf-1ibs-FNAc-wbo8uL

--- Volume group ---
VG Name applivg
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 20.00 GiB
PE Size 4.00 MiB
Total PE 5119
Alloc PE / Size 5119 / 20.00 GiB
Free PE / Size 0 / 0
VG UUID mVbMvv-hN9E-Q3g8-5cJA-gRse-FIHP-wc4rJM

--- Volume group ---
VG Name sysvg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 40.00 GiB
PE Size 4.00 MiB
Total PE 10239
Alloc PE / Size 10239 / 40.00 GiB
Free PE / Size 0 / 0
VG UUID WXFxcS-dlEn-1jTT-mjfK-QtvP-axp7-b6E6fF
 
dietmar said:
You should create partitions inside the VM, then put LVM onto those partitions.
Click to expand...

Hello,

I think it's already done. Y have made a standard install of SLES 11 and define LVM partitioning during install.
The Vm has 4 virtio disks, one for /boot, one for sysvg, one for datavg, and one for applivg.
So i think that the system automatically create these partitions and LVM onto.

Perhaps I'm wrong ?
 
symmcom said:
You can delete the duplicate LVM with the following command:

#dmsetup remove /dev/<vg_name>/<lv_name>
Click to expand...


Hello,

Thank you for your answers ! But i don't understand the actual situation of my LVM;

For the moment, i have destroyed the copy of the VM which conflict with the message "Found duplicate PV..."
I just have 3 Vms on my Proxmox node 01: number 100 (actually stopped), 102 and 109.

All Vm are stored on the same LVM storage, and All Vm use internal LVM.



The problem is that vm's internal VG and LV are visible from Proxmox.


First question : red lines in below results are normal ???
For me only black lines must appear. PV,VG, and LV name in red lines matches to internal LVM number 100.

Vm number 100 is a SLES11.

Vm 102 and 109 are DEBIAN wheezy, using internal LVM, but their PV and VG are not visible here (for me it's normal situation).


Second question : Is there a disfunction in LVM system on this node, and is it dangerous for data integrity ?



Best regards

On command line on the node Proxmox01, pvdisplay show :
--- Physical volume ---
PV Name /dev/sdb1
VG Name dataproxmox-01
PV Size 1.09 TiB / not usable 3.79 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 286069
Free PE 110965
Allocated PE 175104
PV UUID xKCr8C-qqK4-iNL7-yFYW-Ry86-eqI8-k0r457


--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-4
VG Name datavg
PV Size 200.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 51199
Free PE 0
Allocated PE 51199
PV UUID EoUX6o-NuA5-vcsX-cNKt-ml2u-iqGG-n1I3CX

--- Physical volume ---
PV Name /dev/sda3
VG Name pve
PV Size 136.20 GiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 34866
Free PE 4095
Allocated PE 30771
PV UUID L6E9wI-LtEW-Snkj-yFM4-IGnU-8Zn5-fekgsu


--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-3
VG Name applivg
PV Size 20.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 5119
Free PE 0
Allocated PE 5119
PV UUID SpHywq-Vzfj-pE5I-MupA-T5yS-1uvE-ddizjo


--- Physical volume ---
PV Name /dev/dataproxmox-01/vm-100-disk-2
VG Name sysvg
PV Size 40.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 10239
Free PE 0
Allocated PE 10239
PV UUID n0oZ93-MQU1-LSwD-4anA-xDMJ-WSJ2-U09PWv





Pvscan show the same problem :
PV /dev/sdb1 VG dataproxmox-01 lvm2 [1.09 TiB / 43.46 GiB free]
PV /dev/dataproxmox-01/vm-100-disk-4 VG datavg lvm2 [200.00 GiB /0 free]
PV /dev/sda3 VG pve lvm2 [136.20 GiB /16.00 GiB free]
PV /dev/dataproxmox-01/vm-100-disk-3 VG applivg lvm2 [20.00 GiB / 0 free]
PV /dev/dataproxmox-01/vm-100-disk-2 VG sysvg lvm2 [40.00 GiB /0 free]
Total: 5 [1.48 TiB] / in use: 5 [1.48 TiB] / in no VG: 0 [0 ]






For more information here the result of vgdisplay, and lvdisplay


vgdisplay :
VG Name dataproxmox-01
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 57
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 7
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.09 TiB
PE Size 4.00 MiB
Total PE 286069
Alloc PE / Size 175104 / 684.00 GiB
Free PE / Size 110965 / 433.46 GiB
VG UUID FlNS57-OlYU-MpBR-4P9O-WlKr-tom9-By1cpp


--- Volume group ---
VG Name datavg
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 200.00 GiB
PE Size 4.00 MiB
Total PE 51199
Alloc PE / Size 51199 / 200.00 GiB
Free PE / Size 0 / 0
VG UUID Wxu4gQ-2hmV-Pxk6-dQRX-8M3T-3ha2-iKB9wA


--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 136.20 GiB
PE Size 4.00 MiB
Total PE 34866
Alloc PE / Size 30771 / 120.20 GiB
Free PE / Size 4095 / 16.00 GiB
VG UUID IBh9gN-U9PD-xfg7-aaFf-1ibs-FNAc-wbo8uL


--- Volume group ---
VG Name applivg
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 20.00 GiB
PE Size 4.00 MiB
Total PE 5119
Alloc PE / Size 5119 / 20.00 GiB
Free PE / Size 0 / 0
VG UUID mVbMvv-hN9E-Q3g8-5cJA-gRse-FIHP-wc4rJM


--- Volume group ---
VG Name sysvg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 40.00 GiB
PE Size 4.00 MiB
Total PE 10239
Alloc PE / Size 10239 / 40.00 GiB
Free PE / Size 0 / 0
VG UUID WXFxcS-dlEn-1jTT-mjfK-QtvP-axp7-b6E6fF


lvdisplay :


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-100-disk-1
LV Name vm-100-disk-1
VG Name dataproxmox-01
LV UUID A1a73r-7LRn-6xCb-0WCW-KhVa-omEU-DJnuIp
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-22 15:55:02 +0200
LV Status available
# open 0
LV Size 4.00 GiB
Current LE 1024
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-100-disk-2
LV Name vm-100-disk-2
VG Name dataproxmox-01
LV UUID 5jMJJq-hUD5-paoJ-njqi-2iM1-c3Af-iPnzHp
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-22 15:56:11 +0200
LV Status available
# open 0
LV Size 40.00 GiB
Current LE 10240
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-100-disk-3
LV Name vm-100-disk-3
VG Name dataproxmox-01
LV UUID egZzQf-DUWd-VEhS-z8dF-TAms-jYvV-8Buj5A
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-22 15:56:41 +0200
LV Status available
# open 0
LV Size 20.00 GiB
Current LE 5120
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-100-disk-4
LV Name vm-100-disk-4
VG Name dataproxmox-01
LV UUID 9qfq2u-Emrn-Bvud-xeMc-fFin-7dVQ-dX0bqq
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-22 15:57:19 +0200
LV Status available
# open 0
LV Size 200.00 GiB
Current LE 51200
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-102-disk-1
LV Name vm-102-disk-1
VG Name dataproxmox-01
LV UUID KiyqW7-Mqvi-Wcre-2uRV-Y49J-yLX0-mwxX3r
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-29 14:47:40 +0100
LV Status available
# open 1
LV Size 130.00 GiB
Current LE 33280
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:9


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-102-disk-2
LV Name vm-102-disk-2
VG Name dataproxmox-01
LV UUID Vf8zs8-fbvz-nuzt-xL5s-pAVM-9Azw-UWjMlq
LV Write Access read/write
LV Creation host, time proxmox01, 2014-10-29 14:47:40 +0100
LV Status available
# open 1
LV Size 200.00 GiB
Current LE 51200
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:10


--- Logical volume ---
LV Path /dev/dataproxmox-01/vm-109-disk-1
LV Name vm-109-disk-1
VG Name dataproxmox-01
LV UUID qApUnL-sHDd-9eyk-gB3x-PGxW-rTaN-fvSXMX
LV Write Access read/write
LV Creation host, time proxmox01, 2014-11-09 12:33:51 +0100
LV Status available
# open 1
LV Size 90.00 GiB
Current LE 23040
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5


--- Logical volume ---
LV Path /dev/datavg/datavl
LV Name datavl
VG Name datavg
LV UUID 05Mg7K-xv0R-O828-D8WS-wogm-IeBM-YlftM7
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:07 +0200
LV Status NOT available
LV Size 200.00 GiB
Current LE 51199
Segments 1
Allocation inherit
Read ahead sectors auto


--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID 2AngMH-n53l-CUUt-oTij-vVA6-z3u6-EN5EtW
LV Write Access read/write
LV Creation host, time proxmox, 2014-04-01 13:20:48 +0200
LV Status available
# open 1
LV Size 17.00 GiB
Current LE 4352
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6


--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID kBqBOc-ehtx-SacG-nVho-4Mij-hK2D-3OUkRi
LV Write Access read/write
LV Creation host, time proxmox, 2014-04-01 13:20:48 +0200
LV Status available
# open 1
LV Size 34.00 GiB
Current LE 8704
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0


--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID 3ZoMCY-9iJr-M6pb-Jrx2-a0rZ-IlR5-kKIjYb
LV Write Access read/write
LV Creation host, time proxmox, 2014-04-01 13:20:48 +0200
LV Status available
# open 1
LV Size 69.20 GiB
Current LE 17715
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:7


--- Logical volume ---
LV Path /dev/applivg/applivl
LV Name applivl
VG Name applivg
LV UUID 90xIPT-gNi0-obKd-glE0-2yJC-SCUD-pWdluU
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:07 +0200
LV Status NOT available
LV Size 20.00 GiB
Current LE 5119
Segments 1
Allocation inherit
Read ahead sectors auto


--- Logical volume ---
LV Path /dev/sysvg/rootvl
LV Name rootvl
VG Name sysvg
LV UUID kHk7ko-3GPl-8UEH-yAP6-CX44-Y78V-CVrkrW
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:08 +0200
LV Status NOT available
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto


--- Logical volume ---
LV Path /dev/sysvg/swapvl
LV Name swapvl
VG Name sysvg
LV UUID 5dK9ep-uW9f-csyL-KXNC-SiaK-4Qy7-8nPkyp
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:09 +0200
LV Status NOT available
LV Size 10.00 GiB
Current LE 2559
Segments 1
Allocation inherit
Read ahead sectors auto


--- Logical volume ---
LV Path /dev/sysvg/tmpvl
LV Name tmpvl
VG Name sysvg
LV UUID M358Hd-3Un4-GtxH-1F3N-qxzf-6WKf-jlBXbK
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:09 +0200
LV Status NOT available
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto


--- Logical volume ---
LV Path /dev/sysvg/varvl
LV Name varvl
VG Name sysvg
LV UUID ZATqGR-oAaQ-1zFw-GznZ-6Xmp-jXL6-f45GLm
LV Write Access read/write
LV Creation host, time linux, 2014-10-22 16:06:09 +0200
LV Status NOT available
LV Size 10.00 GiB
Current LE 2560
Segments 1
Allocation inherit
Read ahead sectors auto
 
jcb26 said:
Hello,

...

Found duplicate PV n0oZ93MQU1LSwD4anAxDMJWSJ2U09PWv: using /dev/dataproxmox-01/vm-110-disk-2 not /dev/dataproxmox-01/vm-100-disk-2
Found duplicate PV SpHywqVzfjpE5IMupAT5yS1uvEddizjo: using /dev/dataproxmox-01/vm-110-disk-3 not /dev/dataproxmox-01/vm-100-disk-3
Found duplicate PV EoUX6oNuA5vcsXcNKtml2uiqGGn1I3CX: using /dev/dataproxmox-01/vm-110-disk-4 not /dev/dataproxmox-01/vm-100-disk-4
Found duplicate PV n0oZ93MQU1LSwD4anAxDMJWSJ2U09PWv: using /dev/dataproxmox-01/vm-110-disk-2 not /dev/dataproxmox-01/vm-100-disk-2
Found duplicate PV SpHywqVzfjpE5IMupAT5yS1uvEddizjo: using /dev/dataproxmox-01/vm-110-disk-3 not /dev/dataproxmox-01/vm-100-disk-3
Found duplicate PV EoUX6oNuA5vcsXcNKtml2uiqGGn1I3CX: using /dev/dataproxmox-01/vm-110-disk-4 not /dev/dataproxmox-01/vm-100-disk-4

...
Click to expand...

Hi,
this error message shows, that the node see PVs with the same UUID twice:
The same PV (which is inside the VM) on /dev/dataproxmox-01/vm-110-disk-2 and /dev/dataproxmox-01/vm-100-disk-2

I assume you have copy the VM 100 to 110 to got get this issue.
This is normaly no problem, if your lvm.conf is right! You should only use "real" blockdevices for your node-lvm (like sdb, sdc) then you don't see the PVs, which is inside an LV.
Second, like allready someone wrote: use not entire disks inside VMs for lvm - if you have an partition inside the VM the PV is also not visible on the host.

Udo
 
udo said:
Hi,
this error message shows, that the node see PVs with the same UUID twice:
The same PV (which is inside the VM) on /dev/dataproxmox-01/vm-110-disk-2 and /dev/dataproxmox-01/vm-100-disk-2

I assume you have copy the VM 100 to 110 to got get this issue.
This is normaly no problem, if your lvm.conf is right! You should only use "real" blockdevices for your node-lvm (like sdb, sdc) then you don't see the PVs, which is inside an LV.
Second, like allready someone wrote: use not entire disks inside VMs for lvm - if you have an partition inside the VM the PV is also not visible on the host.

Udo
Click to expand...

Hello

Thanks Udo for your answer. You are right !

I made a new SLES11 Vm with partitions (sdb1, sdb2..) to use with LVM.
All works perfectly and the internal vm's PV and LV disappears from Proxmox node.

SLES allow to create LVM directly on /dev/sdb.. and it's not a good way.

Thank you to all people who's answered me so quickly !!
 
jcb26 said:
SLES allow to create LVM directly on /dev/sdb.. and it's not a good way.
Click to expand...
Hi,
this is not SLES-dependet. And "not a good way" would I also not say.

You can easily expand your lvm if you use the whole disk - simply expand the VM-hdd in proxmox and then expand your lvm inside the VM.
With partitions, you need to add another partition, or delete the active partition and add again with bigger size!! (and also reboot)

Udo
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom