Search results

  1. S

    ZFS 2x2TB HDD and SSD LOG + L2ARC - Slow writes, high IO Wait ? Need your advice

    iostat -kxz 5 /dev/sd? Please format your output with code tags.
  2. S

    Proxmox 4.0 ZFS disk configuration with L2Arc + Slog. 2nd opinion

    1. I've though that I've set the record straight on the 940GB L2ARC in post #5, so you just repeat that to argue with me? :) 2. There is no 512 bytes/record. Usually Linux filesystems have 4K blocks, so that will be the minimum record size in the pool. 3. The L2ARC header size varies too (see...
  3. S

    Proxmox 4.0 ZFS disk configuration with L2Arc + Slog. 2nd opinion

    You cannot compare ARC to slog (not ZIL) stating that "ARC RAM" is more important. Even if you have a huge amount of RAM, your sync writes will be written in sync (with sync=standard). Either this is done in a special area in the pool or on your slog (external device for ZIL). That is why it...
  4. S

    disable Intel RC6 in Grub

    Add a /etc/modprobe.d/i915.conf with the following contents options i915 i915_enable_rc6=0 Then update-initramfs -k all -u reboot
  5. S

    Proxmox 4 HA VM Freeze State

    Right. I feel stupid now. I usually use the top right menu in UI, not the contextual one.
  6. S

    Proxmox 4 HA VM Freeze State

    BTW, "freeze" is KVM/QEMU suspend? I want a button for that for non-HA VMs :)
  7. S

    Proxmox 4 HA VM Freeze State

    Live migrating, no, for sure. Restarting the VM on another node, yes.
  8. S

    Proxmox 4 HA VM Freeze State

    Read above about big servers. 30 seconds is for my laptop. For a big memory Dell, 25 minutes is for "Configuring Memory" only. Then you add checks, PCIe devices init, OS startup, VMs startup.
  9. S

    Proxmox 4 HA VM Freeze State

    Actually I was making fun of Proxmox's HA, not your issue. The concept of *High* Availability is not very compatible with 10-15 minutes of downtime because of a (planned) host reboot. Btw, you should try a BIG server reboot (we have a 1.5TB RAM machine) to find out that 15 minutes of reboot time...
  10. S

    Proxmox 4 HA VM Freeze State

    Then we can call it HA* or Best-Effort Availability :)
  11. S

    LXC - Giving absolut maximum cpu

    No, you didn't understand. With fair scheduler, two containers at 100% will have very close to 50% of the host each. Without it, the results may be far away from 50%/each. Again, this scheduling makes sense in a resource (CPU) scarcity context. The fair scheduler will try to allocate fair CPU...
  12. S

    LXC - Giving absolut maximum cpu

    No. It is a "weight". You have 3 CTs: - cpu units 1000 - cpu units 2000 - cpu units 1000 First one will have 25% of CPU time, 2nd 50%, 3rd 25%. This applies relative to full load only. If the machine is idle, it doesn't matter. Think of them as a lottery. The more tickets you buy (cpu units)...
  13. S

    Console does not work anymore

    Incidentally, Safari on El Capitan works for me, but yes, there are all kinds of issues with various heavy-javascript sites in this version.
  14. S

    LXC Ubuntu Samba RAM problem

    Tried to reproduce it on my side and I couldn't. I've copied ~800MB and the "cached" value stayed the same. I have "dir" type containers (on ZFS). Are you by chance have a loopback-mounted one (e.g. on ext4)?
  15. S

    LXC Ubuntu Samba RAM problem

    from the host you can use pct enter <container id> Use top if htop shows all, although in my containers it doesn't.
  16. S

    Backing up proxmox (the host itself) - what and how?

    The LVM layout and configuration is created by the installer. Why would you backup some partitioning information? Maybe you will need to restore to another hard-drive with a different size.
  17. S

    Convert KVM image to LXC

    You make an archive of your / (after you shutdown all the services, like databases) excepting /proc/*, /sys/*, /run/* and import it in your LXC container. Worst case, you might need to fiddle with systemd. A better way to do it would be to mount the KVM disk inside the host and do the...
  18. S

    Backing up proxmox (the host itself) - what and how?

    Your custom stuff is... custom handled. I was talking about backing up for a quick restore: install from iso, copy back the needed files (from /etc/pve/qemu/*.conf and /etc/pve/lxc/*.conf), the network configuration and you are done (again, assuming you have a separate backup or external storage...
  19. S

    Backing up proxmox (the host itself) - what and how?

    If you backup your storage, /etc/pve folder and /etc/network/interfaces should be enough to put a new install up in no time.
  20. S

    too low open file limit

    @Ovidiu: do it in hypervisor. You cannot alter it inside LXC/OpenVZ.