Search results

The firmware is Firmware version: 15.10.01.00. Is it worth update to P19 or P20?

LSHW # lshw -class disk -class storage *-sas description: Serial Attached SCSI controller product: SAS2308 PCI-Express Fusion-MPT SAS-2 vendor: LSI Logic / Symbios Logic physical id: 0 bus info: pci@0000:04:00.0 logical name: scsi0...

EXT4 single drive (SAMSUNG 860 Pro) FSYNCS/SECOND: 207.53

fio --filename=test --sync=1 --rw=randread --bs=4k --numjobs=1 --iodepth=4 --group_reporting --name=test --filesize=1G --runtime=300 && rm test READ: bw=526MiB/s (552MB/s), 526MiB/s-526MiB/s (552MB/s-552MB/s), io=1024MiB (1074MB), run=1945-1945msec, iops avg=149850.67 (system) READ: bw=526MiB/s...

After upgrade to zfs 0.8.3, the results is more: FSYNCS/SECOND: 2811.57 FSYNCS/SECOND: 394.92 FSYNCS/SECOND: 359.10 But why the hell the system pool is almost 7 times faster at the same controller.

Got problems with performance of Proxmox: I have got: - Proxmox 6.x (clean install from ISO)m - H220 SAS card in IT mode, - 6x different SSD drives: 2x Goodram 120GB (system) 2x Samsung 860 PRO 256GB (pool1) 2x IRDM Pro 1TB (pool2) hdparm -t -T /dev/sd(a-f) gets about 520MB/s read but when I...

I got the same problem. # pveversion pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-24-pve) 0.7.13-pve1~bpo2 The dataset is unmounted right now. grep datasetname /proc/*/mounts didn't show anything. lsof | grep datasetname also

This fix cause instability - read more at https://github.com/zfsonlinux/zfs/issues/9346

All Clear.

https://github.com/zfsonlinux/zfs/commit/e5db31349484e5e859c7a942eb15b98d68ce5b4d This is an antitodum of slow write performance from 0.8.x. Do You plan to put this to actual version of proxmox?

The other thing is to change open_files_limit. You need to also set in '/etc/pve/lxc/CTID.conf' lxc.prlimit.nofile: 100000 Maybe this option should be set from Proxmox GUI?

Ok - If You use unprivileged type of LXC, You need to set Feature: Nesting=1 from GUI for mysql or completly disable apparmor. Solved.

I don't know is this a good place to post a bug: I created CT with template debian-10 and then installed mariadb. root@dev1:/var/www/html/dev/include# systemctl status mariadb.service * mariadb.service - MariaDB 10.3.15 database server Loaded: loaded (/lib/systemd/system/mariadb.service...

Please add ZFS 0.8.1 to Proxmox 5.x or Release Proxmox 6.0 as soon as Debian/Buster comes out. It will get our machines so much performance gain and TRIM for SSD's whitch is very important.

If You can reproduce it thats fine. So I mark this thread as [SOLVED] as it is being procesed by proxmox bugzilla for now.

The problem in my case is sold. If You don't want to make a changes in code in this part mark post as [SOLVED].

I need to turn off: CT--> Firewall --> Options --> IP Filter And the error disappears. So probably this part of code not suits all cases.

The error is generated constantly Apr 30 13:10:00 v3 systemd[1]: Starting Proxmox VE replication runner... Apr 30 13:10:01 v3 systemd[1]: Started Proxmox VE replication runner. Apr 30 13:10:06 v3 pve-firewall[11910]: status update error: unable to apply firewall changes Apr 30 13:10:16 v3...

After disabling that option: # ebtables-save # Generated by ebtables-save v1.0 on wto, 30 kwi 2019, 13:08:48 CEST *filter :INPUT ACCEPT :FORWARD ACCEPT :OUTPUT ACCEPT And after enabling the rules are restored

Ok, I've got it: $ pve-firewall stop; pve-firewall start -debug ebtables : unable to update chain 'veth104i0-OUT-ARP' ebtables : unable to update chain 'veth106i0-OUT-ARP' ebtables : unable to update chain 'veth106i1-OUT-ARP' ebtables : unable to update chain 'veth167i0-OUT-ARP' ebtables ...