Search results

Ok, effectively, I have files with ACL set but acl package not install on LXC... After install package and remove all ACL (not use in my use case), backup is now OK, thanks for your help !

In this order, why all others LXC can backup in same mode, same node, same temp dir? This is a part of backup on last night: INFO: Backup started at 2021-04-15 03:37:25 INFO: status = running INFO: CT Name: [lxc1] INFO: including mount point rootfs ('/') in backup INFO: mode failure - some...

Hi, I have a backup problem on Proxmox 6.3, on a hundred VMs backed up daily, I have no errors, for 2 of them, it goes into error in suspend mode, if I do the backup in stop mode manually , no problem. Bakckup are send to NFS, generate on local tmp folder. For both, I have this log on backup...

Thanks for your help, I reinstalled old server with latest Proxmox version on ZFS instead of soft raid by OVH. Clearly, it's better, with no VM started, I hit 100+ FSYNCS/Second (not the best, but at least double old value). Next step, reinstall new server on ZFS and check if perf is better or...

Sorry I miss your comment # mdadm --detail /dev/md2 /dev/md2: Version : 0.90 Creation Time : Tue Nov 27 15:01:41 2018 Raid Level : raid1 Array Size : 20478912 (19.53 GiB 20.97 GB) Used Dev Size : 20478912 (19.53 GiB 20.97 GB) Raid Devices : 3 Total Devices : 3...

Sorry for the response time, long week-end with current event... I can shut down all VM yesterday, and I have same perf than old server when all VM is shutdown, so it's seems possible to get better perf # pveperf /var/lib/vz CPU BOGOMIPS: 60798.40 REGEX/SECOND: 4416748 HD SIZE...

Yep, I backup on old and restore after scp, with this configuration: All VM are LXC Containers I take screen on [nodename] > storage local ([nodename]) (at the end of VM list) For the qm config, I have an error.... (106 is on the server).... # qm config 106 Configuration file...

On old server: # mdadm --detail --scan ARRAY /dev/md2 metadata=0.90 UUID=b35014e9:92c5dc37:a4d2adc2:26fd5302 ARRAY /dev/md4 metadata=0.90 UUID=655cac0e:41e7cb4e:a4d2adc2:26fd5302 On new # mdadm --detail --scan ARRAY /dev/md2 metadata=0.90 UUID=d090d79b:04b40376:a4d2adc2:26fd5302 Really...

On new server, each VM has his own disk, for example: Disk /dev/loop55: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes For me, it's an evolution between...

Old Server CPU: 8 total core Old server RAM Old server Disk

Ok, If some information is missing, ask and I add them. New Server Cpu: Same information for 7 other core New server RAM New Server Disk (I don't show /dev/loopXX for readibility)

Effectivelly, mdadm is default soft raid on OVH server, but, on your old server, we don't have this issue, so why this happen on new servers? For pveperf, I launched all the VMs on the old server and have ten times better performance, so, it's seem possible to improve perf, even on mdadm ?

On old server, we have: # smartctl -a /dev/sda Device Model: HGST HUS726020ALA610 Seems to be old version of HDD ?

I don't know if HDD as SMR or how to know this # smartctl -a /dev/sda Model Family: HGST Ultrastar 7K6000 Device Model: HGST HUS726040ALA610

Hello, We migrate old three server on proxmox 5.2 to three new server EG-32 on OVH (Serveur EG-32 - Xeon E3-1270v6 - 32GB - SoftRaid 2x4To) with proxmox 6.2. In december, we migrate all VM on new servers, since, we face on low FSYNCS/SECOND and high IO delay, we don't have any issue on old...