Search results

You might use a mirrored ZIL for safety, but it will most likely not affect performance at all (or hinder it a bit), and take up unnecessary space. You really need the ZIL when you have a pool of slow drives, no advantage when using SSDs only. Same for L2ARC. Forget both, stripe the drives for...

@spirit You are mixing up entirely different things. It's not consumer grade SSD that's need to be avoided, it's TLC drives, which - due to their complex write operations - are much slower to write than MLC drives. This has nothing to do with the fact that the ZIL buffers sync writes only...

Thanks for this information. Problem is, assigning specific cores to containers would seriously impair fair scheduling on the host. As it's impossible to predict how much load one container would put on a specific core, it would be very hard to divide the available cores evenly between...

If you actually used containers in production, you would know what we are talking about. While you might have unconditional love towards Proxmox 4 and LXC, and want to get rid of all "old technology" as soon as possible, the reality is far more complicated than that. Many organisations actually...

Search is your friend, why not use it? You can restore LXC backups to OpenVZ with a bit of work, I have posted a step-by-step guide here: https://forum.proxmox.com/threads/can-lxc-backup-be-restored-to-openvz.25262/#post-128805

So I streamlined the conversion of LXC containers back to OpenVZ, if anyone else needs it. I got the information about missing devices from the OpenVZ P2V tutorial: https://openvz.org/Physical_to_container Here are the steps to take converting LXC to OpenVZ: Prerequisites I have an NFS server...

We've had problems with it before (migration errors mainly), but it's still miles better than the backup-restore you are forced to use with LXC guests, causing several hours of downtime for large guests. Consider yourself lucky... Unfortunately, we have many guests where the overhead caused by...

I have to agree with @shukko and @PLE We've had to actually revert our cluster back to PVE 3.4 (and our containers to back OpenVZ) due to issues that - for now - are making PVE 4.1 and LXC not ready for production: - There is no live (or even suspended) migration of LXC containers - There is...

According the the ZFS on Linux github, they just released a new version, and it's compatible with 2.6.32 - 4.4 kernels. https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.4 Would it be possible to release it for both 3.4 and 4.1? If yes, then we could test the checksum / data corruption...

Thank you for this tip. However I sincerely hope that @dietmar follows this thread, and will help us bughunting by releasing the same ZFS packages for PVE 3.4 as they include in PVE 4.1.

Yes I did have the swap on ZFS (not sure if ZVOL, default Proxmox ZFS RAID10 install). I did not have ANY virtual machines running, I only restored containers and VMs to test for data corruption. Also swap was not or rarely used, as no guests were running. I have checked numactl with all the...

Well, current ZFS release 0.6.5.3 contains hundreds of important bugfixes since 0.6.3 (among them many deadlocks and kernel panics), so I really hope you will find the time to include it in your upcoming PVE 3.4 fixes... https://github.com/zfsonlinux/zfs/releases Also including identical ZFS...

Currently Proxmox VE 3.4 includes the following LVM and ZFS versions: lvm2: 2.02.98-pve4 zfs: 0.6.3-3~wheezy Proxmox VE 4.1 has newer versions, and those have many bugfixes (especially for ZFS 0.6.5), and new features (like SSD caching in LVM2). - Is it possible to backport these newer...

We still had this issue occur a few times in the past months on Proxmox 3.4 nodes, but only when manually stopping the (snapshot) backup from the web interface. Then all IO stops, and load starts to increase indefinitely. Only hard reset can restart the nodes. Proxmox 3.4 on Adaptec RAID10...

I have tried to restore LXC backups to OpenVZ with the following procedure: - unpacking the tar.lzo (first lzop -d, then tar xvf) - recreating the original OpenVZ config file by creating an empty container with identical specs - copying config file from /etc/pve/openvz/XXX.conf into the archive...

Since we reported that this technology preview does not work for LXC containers at all, the Proxmox dev team ceased all communications regarding this issue. We have no answer here, nor any reaction to my bugreport, total radio silence. Which is a shame, since snapshot backups were such an...

Unfortunately, LVM thin support does not work for LXC containers. When trying to restore a container to an lvm-thin pool, the web interface gives the following error: Any news on when will LVM thin be supported by the web interface, and when will it support containers?

Any news on this?

We have migrated several LAMP containers to LXC, and experiencing repeated MySQL connection problems since then. The problems only happen inside the containers: Apache / PHP sometimes can't connect to the MySQL running on localhost. There were numerous occasions where MySQL has "gone away"...