hi,
for short: I have changed my Debian Xen to a ProxMox host, with Enterprise repository enabled.
Today I wanted to create a new VM on a single VE Host, but I get "proxy detected vanished client connection" messages. It seems, that these problem are storage related, because it happens only, If I do anything on storage things.
A *scan shows me:
vgscan takes a lot of time ... (up tp 60sec=
Only "neko" VG is the PVE host, all others are inside the VMs, like "rootvg", "sharevg" ...
I tought, that with a normal installation (via ISO) from Proxmox, there is LVM filter active, but "diff" shows me no changes ...
@work, I don't see the same behavior on my 10 node Cluster.
I added /dev/md0 to lvm.conf as filter. That seems to be a good workaround ..
any suggestions?
for short: I have changed my Debian Xen to a ProxMox host, with Enterprise repository enabled.
Today I wanted to create a new VM on a single VE Host, but I get "proxy detected vanished client connection" messages. It seems, that these problem are storage related, because it happens only, If I do anything on storage things.
A *scan shows me:
Code:
lvscan
inactive '/dev/datenvg/wwwfs' [5.00 GiB] inherit
inactive '/dev/rootvg/rootfs' [3.00 GiB] inherit
inactive '/dev/rootvg/swapfs' [1.00 GiB] inherit
inactive '/dev/sharevg/seafcrypt' [30.00 GiB] inherit
inactive '/dev/data/vmail' [30.00 GiB] inherit
ACTIVE '/dev/neko/rootfs' [5.66 GiB] inherit
ACTIVE '/dev/neko/swapfs' [1.86 GiB] inherit
ACTIVE '/dev/neko/varfs' [1.86 GiB] inherit
ACTIVE '/dev/neko/varlogfs' [4.42 GiB] inherit
inactive '/dev/neko/backup-sys' [80.00 GiB] inherit
inactive '/dev/neko/backup-disk' [14.00 GiB] inherit
ACTIVE '/dev/neko/backup-crypt' [700.00 GiB] inherit
ACTIVE '/dev/neko/pve-data' [500.00 GiB] inherit
ACTIVE '/dev/neko/vm-100-disk-1' [6.00 GiB] inherit
ACTIVE '/dev/neko/vm-100-disk-2' [35.00 GiB] inherit
ACTIVE '/dev/neko/vm-101-disk-1' [6.00 GiB] inherit
ACTIVE '/dev/neko/vm-102-disk-1' [6.00 GiB] inherit
ACTIVE '/dev/neko/vm-103-disk-1' [6.00 GiB] inherit
ACTIVE '/dev/neko/vm-103-disk-2' [80.00 GiB] inherit
ACTIVE '/dev/neko/vm-103-disk-3' [50.00 GiB] inherit
ACTIVE '/dev/neko/vm-104-disk-1' [6.00 GiB] inherit
ACTIVE '/dev/neko/vm-104-disk-2' [10.00 GiB] inherit
pvscan
PV /dev/neko/vm-104-disk-2 VG datenvg lvm2 [10.00 GiB / 5.00 GiB free]
PV /dev/mapper/neko-vm--100--disk--1p2 VG rootvg lvm2 [6.00 GiB / 2.00 GiB free]
PV /dev/mapper/neko-vm--101--disk--1p2 VG rootvg lvm2 [6.00 GiB / 2.00 GiB free]
PV /dev/mapper/neko-vm--102--disk--1p2 VG rootvg lvm2 [6.00 GiB / 1.51 GiB free]
PV /dev/neko/vm-103-disk-3 VG sharevg lvm2 [50.00 GiB / 20.00 GiB free]
PV /dev/neko/vm-103-disk-2 VG datenvg lvm2 [80.00 GiB / 55.00 GiB free]
PV /dev/neko/vm-100-disk-2 VG data lvm2 [35.00 GiB / 5.00 GiB free]
PV /dev/md0 VG neko lvm2 [1.82 TiB / 350.22 GiB free]
vgscan takes a lot of time ... (up tp 60sec=
Code:
Reading all physical volumes. This may take a while...
Found volume group "datenvg" using metadata type lvm2
Found volume group "rootvg" using metadata type lvm2
Found volume group "rootvg" using metadata type lvm2
Found volume group "rootvg" using metadata type lvm2
Found volume group "sharevg" using metadata type lvm2
Found volume group "datenvg" using metadata type lvm2
Found volume group "data" using metadata type lvm2
Found volume group "neko" using metadata type lvm2
Only "neko" VG is the PVE host, all others are inside the VMs, like "rootvg", "sharevg" ...
I tought, that with a normal installation (via ISO) from Proxmox, there is LVM filter active, but "diff" shows me no changes ...
@work, I don't see the same behavior on my 10 node Cluster.
I added /dev/md0 to lvm.conf as filter. That seems to be a good workaround ..
any suggestions?
Last edited: