Search results

If you have cash to spend (RSF-1): https://www.youtube.com/watch?v=JZ2PK-AXZ0A Otherwise use UPS to guard your storage server and Cheap: multiple nics using LACP Less cheap: Configure multipath on proxmox to storage server preferable using LACP on each path

From a single SSD: Jobs: 1 (f=1): [m(1)] [97.8% done] [78518KB/26377KB/0KB /s] [19.7K/6594/0 iops] [eta 00m:01s] test: (groupid=0, jobs=1): err= 0: pid=30053: Wed Dec 5 07:43:33 2018 read : io=3070.4MB, bw=68841KB/s, iops=17210, runt= 45670msec write: io=1025.8MB, bw=22998KB/s, iops=5749...

This simply means that LVM is used (dm == DeviceMapper)

A storage solution based on Omnios using ZFS over iSCSI is rock stable and gives very good performance given the ZFS pool is properly configured. A raid10 like setup gives the best iops for the sake of available storage. This in depth article is recommendable...

This /dev/vmtank/disks/vm-129-disk-1 is a local disk so you are not using ZFS over iSCSI. ZFS over iSCSI requires a remote server exposing a ZFS pool for which there is support in the ZFS over iSCSI storage type. You cannot migrate a local disk exposed via iscsi.

What console solution? Generally I find keyboard support considerably better when using spice console, so if you haven't tried spice try it.

This file is mentioned in man.db but is not part of Debian.

I was referring to the proxmox checkbox 'discard' to prevent confusion not whether the filesystem supports discard or not. Many users have 'discard' checked while running fstrim on a regular basis which is foolish.

If you run fstrim there is no need for discard. fstrim does not rely on nor does it use discard. discard is only used in combination with a filesystem delete.

Checking discard option means that every time you mark a block of data as free due to deleting something a corresponding scsi unmap command will be sent to the disk controller (virtio-scsi) which passes this information through to the physical disk where your disk image hosted. If discard option...

This is wrong. Having this option set means running discard every time you delete something rendering the scheduled trim unnecessary. Either using option discard or run trim on a regular basis.

Not only restricted in number of vlans but also restricted in the vlan numbering. If they have to choose a byte to store vlans why choose a signed byte! There is no such thing as a negative vlan number.

This might indicate that only 128 vlans is supported in hardware but I would expect this to be a relative number and not limited to 1-129

use the gtls module: https://www.rsyslog.com/doc/v8-stable/tutorials/tls.html

So you are sending all syslog data in clear text over the network! Seems scary to me.

If snapshot is missing critical and you must use a SAN solution you need to purchase a SAN which supports snapshotting LUN's on the SAN side. For IBM I think you need to look at Storwize.

Hi Dennis, You asked exactly the same question back in July https://forum.proxmox.com/threads/proxmox-cluster-with-san-storage.40756/#post-218816 where you got exactly the same answers! So now it would be time for you to show that you have done some homework;-)

What physical nics do you have in your proxmox host?

mlx4_core has this option: log_num_vlan "Log2 max number of VLANs per ETH port (0-7) (int)" You could try to see if using this changes anything.

Have you tried Mellanox's own Linux driver? http://www.mellanox.com/page/products_dyn?product_family=27