PROXMOX V5.2 - Backup, Restore, Clone too slow after upgrading PVE 3.4 to 5.2

[yboujraf]

Dear,

Since I have upgraded my pve 3.4 to 5.2, now backup, clone, restore are very sloww and block access to my virtual machine.

Here you can find all the setup done :

• File format

1. PVE root, swap and data are in ext3 same as used with PVE 3.4
2. NAS synology is using ext4 (connect in nfs)

• Network

1. PVE using Bond and vmbr
2. HP V1910 using LACP for PVE and NAS
3. NAS using Bond 4x 1Gb/s

Question, after googled and browsed the forum, Is it better to format in EXT4 instead of EXT3 previously to fix the issue or may be a wrong settings.

Best regards,
Youssef

 

[wolfgang]

Hi,

the reason is that ext4 uses write barriers and ext3 not.
If you have an intel CPU the meltdown and spectre patches can cost up to 15% performance.

 

[yboujraf]

Dear,

Thanks for your reply.

FYI, I have AMD.

## CPU

# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                24
On-line CPU(s) list:   0-23
Thread(s) per core:    2
Core(s) per socket:    6
Socket(s):             2
NUMA node(s):          4
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 2
Model name:            AMD Opteron(tm) Processor 6344
Stepping:              0
CPU MHz:               3111.215
CPU max MHz:           2600.0000
CPU min MHz:           1400.0000
BogoMIPS:              5200.39
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
L3 cache:              6144K
NUMA node0 CPU(s):     0-5
NUMA node1 CPU(s):     6-11
NUMA node2 CPU(s):     12-17
NUMA node3 CPU(s):     18-23
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

## /ETC/FSTAB

# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/pve-root /               ext4    rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0
/dev/mapper/pve-swap none            swap    sw              0       0
/dev/mapper/pve-management /mnt/vm-management   ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/mapper/pve-vm--data /mnt/vm-data   ext4 rw,relatime,barrier=0,data=ordered 0 0

Now, after formatting, creating a new fresh raid 5, create Volume group and logical Volumes, formatting in EXT4
and changed in the fstab : /dev/mapper/pve-management /mnt/vm-management ext4 rw,relatime,barrier=0,data=ordered 0 0


Question :

- when connecting Proxmox server the NAS through a switch unmanaged, the FSYNC is > 3500 FSYNC/SECOND.
- when connecting Proxmox server, the NAS through a managed switch with LACP enabled and VLAN the FSYNC is arounf 600.

Any idea if my Network setup is ok :

==== info about HP V1910 ====

interface Bridge-Aggregation2
 link-aggregation mode dynamic

 #
interface GigabitEthernet1/0/3
 description BOND NAS SYNOLOGY
 stp edged-port enable
 port link-aggregation group 2
#
interface GigabitEthernet1/0/4
 description BOND NAS SYNOLOGY
 stp edged-port enable
 port link-aggregation group 2
#
interface GigabitEthernet1/0/5
 description BOND NAS SYNOLOGY
 stp edged-port enable
 port link-aggregation group 2
#
interface GigabitEthernet1/0/6
 description BOND NAS SYNOLOGY
 stp edged-port enable
 port link-aggregation group 2

# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp3s0f0

iface enp3s0f0 inet manual

iface enp2s0 inet manual

iface enp3s0f1 inet manual

auto bond0
iface bond0 inet manual
    bond-slaves enp3s0f0 enp3s0f1
    bond-miimon 100
    bond-mode 802.3ad
    bond-xmit-hash-policy layer2
#Bond0_LACP

auto vmbr0
iface vmbr0 inet static
    address  192.168.0.5
    netmask  255.255.255.0
    gateway  192.168.0.1
    bridge-ports bond0
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094
#vmbr0_Bridge

Thanks a lot if anybody could verify.

Best Regards,
Youssef