Search results

Or zswap... Or buy more RAM, and turn swap off! The last time I had swap on my server was some 5-6 years ago...

Check VMware vSphere documentation. I bet you still find there something like "keeping time in VM using vmware-tools is NOT recommended". For very good reasons which were discussed on VMware-web many times... Proper solution is using NTP-client. Actually, I'm running stratum-1 ntp-server on one...

I hope PVE 5.0 will be released "when it is ready". As you can see yourself, work on PVE 5.0 is still going on. Ultimately, it only 2 weeks since Debian9 was released. We all want PVE 5.0 asap, but let's be patient...

It might be "normal" in KVM, but I have never seen this in Xen or ESXi. Clock in VM (be it KVM, LXC or whatever) should be related to HW-clock in host (with host-VM timezone delta considered), which never drifts under load. So why should VM-clock drift then? But anyway, you should never do...

If running backup job slows down time in VM, then there is definitely something wrong. This should not happen! BTW, even with ntp-client you might run into problems. NTPd can correct time by either "slewing" (speeding up/slowing down) of timer frequency or by "stepping" (rapid change in single...

Have you gone mad? Putting DATA and backups on raid0 and system on raid1???

I did not compare mdadm vs zfs, but mdadm vs hw-raid, because your statement was: That's simply not true. Both mdadm and hw-raid (and zfs-raid) have advantages and disadvantages. Period.

Did it generage "negligible" load? I doubt. Calculating parity with that much drives takes some cpu-time. And what's even worse, if you do not have cpu/core reserved exclusively for mdadm, other apps will be competing for cpu-time and slowing down i/o. Not problem for lightly/moderately loaded...

Yes, for raid1/0/10. But did you ever try reconstruction of raid5/6 array with ~20 drives? AFAIK, mdadm is supported only by linux. HW-raid is supported by any major OS. In every case, you need driver (either as part of linux-kernel sources, OS-installation disk, or as extra sw-package). Only...

Really? You said "every" (sic!) part of mdadm is better than hw-raid. Ok, so let's discuss a few things: System cpu-load (especially during array-reconstruction): lower with mdadm, or with hw-raid? Or OS-support: better with mdadm, or hw-raid? Array reconstruction: easier on mdadm, or hw-raid...

You can't mean this seriously...

The only error on the 1st screenshot clearly states it can not write to /dev/nvme0n1p1, that is the 1st partition on nvme0n1. Maybe that orphan partition (created with PVE4.4) is somehow "not compatible" with PVE5.0b2 installer. Sure it is not needed, because PVE5.0b2 installer tries to wipe out...

It is always good to have the latest cpu-microcode installed, true. But this seems to me more like problem with proper hardware detection, or device-names. That nvme-disk is first correctly detected as /dev/nvme0n1, but why are there already 3 partitions (p1,p2,p3)? I'd recommend to remove all...

Just guessing: CPU Ryzen & chipset B350 is still quite new HW, so maybe it is not yet fully supported by Linux...

Waiting for it too. But let's not be too hasty. Better later and rock-stable... I hope PVE 5.0 "final" will include the latest Intel microcode update (although Debian can not include it in installation medium due to licensing issues). Nearly all Skylake/Kabylake CPUs (incl. xeon E3) have bug in...

That should be your least concern. More serious problem of missing "trim" is performance degradation over time. R/W-speed can drop to fraction of what SSD had as new. Consumer-SSDs are severely impacted by this, but even high-end industry-level SSDs suffer. The only solution (except of moving to...

If you store VM/LXC on zfs-pool, bear in mind that zfs on linux does not support TRIM yet...

You'd better learn that "systemctl" command! Soon it will be easier to remember what is *not* contolled by systemd... :-)

When we are at it, maybe you could update other templates too (alpine, arch, gentoo...)

Debian 9 "Stretch" has been officially released. I hope PVE 5.0 will follow soon...