Recent content by qubozik

Got it. Thank you. Replied to bug with links to perf reports.

@Stoiko Ivanov Thank you. I have filed the following bug: https://bugzilla.proxmox.com/show_bug.cgi?id=1943 I am trying to get the perf reports for you, but I am seeing this error when trying to run perf: root@node3:~# perf /usr/bin/perf: line 13: exec: perf_4.15: not found E...

@Alwin Does the latest kernel as of this comment in the pve no sub repo include the fixes described previously? 4.15.18-2-pve #1 SMP PVE 4.15.18-20 (Thu, 16 Aug 2018 11:06:35 +0200) x86_64 GNU/Linux

I, too, am seeing this issue once again. Using 4.15.17-2-pve. This was working at one point in time. Some time in the 4.13 series. Looks like the issue is back with the 4.15 series?

Hey! :) Perhaps read this: https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache Test different caching settings. Take caution when enabling write-back if you do not have a battery backed RAID card. Good luck!

+1

I am seeing this, too. This does not occur with Ubuntu or Debian templates. I checked file descriptor limits, open thread limits, etc. All seems well. Anyone have any ideas?

@chs_voks, Were you able to get anywhere with this? I am seeing this same issue every 1-2 weeks on one of my nodes and having trouble pinpointing a root cause. If not, anyone else have any information?

Just wanted to follow-up on this in case anyone has the same issues... So, the multicasting issues were caused by the enabled "Anti-DDoS" features which were enabled within the switch. I disabled those and was then able to use omping to test multi-cast between the nodes. Something still...

Awesome! Sorry it didn't work out, but thanks for the contribution. I'll take a look at it.

Hello! I have a two node cluster. NodeA in the cluster does not appear to have a multicast address. When running the following command this is the output: # corosync-cmapctl -g totem.interface.0.mcastaddr Can't get key totem.interface.0.mcastaddr. Error CS_ERR_NOT_EXIST NodeB will show a...

Ah... Sorry to hear there isn't a more apparent reason this is happening. I am using Proxmox 4.2.

I'm 4.2. No IO issues for me. I have about 6 VMs with daily backup schedules. All have been running smoothly since the switch to NFS. I even have backed all of them up manually yesterday and today with no issues. Goes without a hitch. Perhaps there is an issue with the network connection to...

Hello, I didn't mount the NFS manually. I just configured it in the Proxmox GUI for adding an NFS server as a storage option. Once you add the server there, you will see the exports are automatically populated by Proxmox. Just select the export which belongs to your account. Then put the...