Search results

  1. mir

    [SOLVED] TRIM SSDs

    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.
  2. mir

    VLAN with tag above 126 problem

    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.
  3. mir

    VLAN with tag above 126 problem

    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
  4. mir

    Remote Syslog

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

    Remote Syslog

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

    Recommendations Needed (Proxmox Setup)

    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.
  7. mir

    Recommendations Needed (Proxmox Setup)

    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;-)
  8. mir

    pfSense gateway warning packet loss

    What physical nics do you have in your proxmox host?
  9. mir

    VLAN with tag above 126 problem

    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.
  10. mir

    VLAN with tag above 126 problem

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

    pfSense on Proxmox - 500mbps on 1G line

    Performance is always dependent on hardware so if your nics are not quality hardware you will never be able to saturate a Gb uplink. Quality hardware does not include Realtek.
  12. mir

    proxmox HA on shared SAN storage

    OCFS2 is abandon ware so hardly a candidate for customers running in production!
  13. mir

    Proxmox cluster reboot

    An even number of nodes is always a bad thing for deciding quorum.
  14. mir

    What open source solutions are available to use "ZFS over iSCSI with Proxmox"?

    This is strange since the drivers for Mellanox 10Gbit in FreeNAS/FreeBSD is the ported drivers from OmniosCE. I have no problems with either Mellanox 10 or 20 Gbit in both Omnios and FreeNAS.
  15. mir

    Shared Storage for a PVE Cluster

    I would suggest Omnios which is now OmniosCE.
  16. mir

    proxmox HA on shared SAN storage

    If you do not require your storage to be HA as well ZFS over iSCSI is a very stable solution.
  17. mir

    proxmox HA on shared SAN storage

    Most enterprise SAN's has the ability to make snapshots of LUN's so instead of making snapshots in proxmox you make the snapshots on the SAN.
  18. mir

    How can you maintain the cluster to continue to works after some nodes/datacenter down

    And if you shut down two monitor servers?
  19. mir

    How can you maintain the cluster to continue to works after some nodes/datacenter down

    In generel clusters with an even node numbers is a disaster waiting to happen. Always use odd numbers for nodes in a cluster or in Ceph terms odd numbers for monitors.
  20. mir

    qdevice for a scaleable cluster

    nodes for quorum must be physical. Using a VM for quorum is dangerous and plain stupid.
Top Bottom