Search results

Another thing to take into consideration is storage efficiency. You should try to match volblock size with actual size of the written blocks. If you primarily do 4k writes, like most database systems, then favor a volblock size of 4k.

I have narrowed it down to a problem when I choose to have the syslog displayed and it is not specific to any browser. What happens is that pveproxy simply becomes unresponsible and a systemctl restart pveproxy.service is required to make the gui functional again.

You cannot compare 60.x to 66.x. They are to different. The same goes for comparing 52.x against 60.x.

Maybe you could explain the details of how it works on the wiki when you have it all working? Benchmarks are also welcome ;-)

Hi Wolfgang, Ditto here: dpkg -s firefox-esr Package: firefox-esr Status: install ok installed Priority: optional Section: web Installed-Size: 162542 Maintainer: Maintainers of Mozilla-related packages <team+pkg-mozilla@tracker.debian.org> Architecture: amd64 Version: 60.6.1esr-1

Try reading this: https://serverfault.com/questions/824932/why-zfs-file-system-is-not-shared-after-boot/824956

Hi all, Anybody else experiences problems with the webui and firefox-esr? If I have the webui running in a tab of firefox-esr for several hours the tab will crash and the only way to fix it is to close the tab. The same thing does not happen with the normal firefox.

Without performance numbers it is impossible to give you any advice.

After installation a proxmox node always defaults to use the pve-enterprise repository which, in case of a missing subscription, will always return an empty list and restrict to fetching packages from official Debian repositories. Always have this in mind or visit...

And match it with this one: dpkg -s corosync-qdevice Package: corosync-qdevice Status: install ok installed Priority: optional Section: admin Installed-Size: 504 Maintainer: Debian HA Maintainers <debian-ha-maintainers@lists.alioth.debian.org> Architecture: amd64 Source: corosync Version: 2.4.4-pve1

Disgard my first answer and read what I have just written ;-)

You need to ensure that you have the corosync package from proxmox installed: dpkg -s corosync Package: corosync Status: install ok installed Priority: optional Section: admin Installed-Size: 1431 Maintainer: Debian HA Maintainers <debian-ha-maintainers@lists.alioth.debian.org> Architecture...

I have may a request to the devs for your card in 151022 LTS

I only run LTS releases so I haven't tried any later versions than 151022. You could try asking for help here: https://illumos.topicbox.com/groups/omnios-discuss I think you are facing a network/comstar related problem.

What version of omnios do you use?

If you run this command on omnios: stmfadm list-lu -v Does all your Luns show this? Writeback Cache : Enabled

Your storage box seems to be working perfectly. The only thing I can think of is network related since iSCSI performance is very picky when it comes to network configuration and especially MTU. What MTU are you using on the network handling iSCSI traffic? I personally use infiniband so on my...

Could you show output from zpool get all pool1 zfs get all pool1 on omnios

Your Intel Optane 900p should not be where your worries are: https://www.servethehome.com/exploring-best-zfs-zil-slog-ssd-intel-optane-nand/

Try using fio for disk benchmark using this (copy below as input to a file to use as input to fio) # This job file tries to mimic the Intel IOMeter File Server Access Pattern [global] description=Emulation of Intel IOmeter File Server Access Pattern [iometer]...