Search results

Well… I don't know, what a "massive" rpool on a pve host will give you, since you're using different ZPOOLs for your VMs/containers anyway, but yes - the wear-levelling is up to the drives internals and you shouldn't need to worry about it nowadays. Long gone are days, when we had to...

Aha… ok, so this will be my final post to this threat and that's only for technical reasons… I don't support this way of making money… your i/o delay is way too high and that would either indicate a broken drive or the lack of IOPs, which can be countered by installing a SSD. I'm out…

That would be the latter… SSDs will have to take care of their wear levelling themselves. This is nothing you leave to the file system. If you've got bigger SSDs and you can male good use of them as boot disks, by all means, go for it. However, I always prefer to keep the boot disks as small as...

Soo… without any liability… I have never seen the CPU performance being the bottleneck in any of my VM servers - it has been always RAM or storage throughput. 173ms average seek time is a horror to my eyes and if I'd only have one shot, I'd go with that. However, this seems to be the drive where...

Remove the IP from enp2s0, the rest looks correct. And maybe take a look at the manual, no? Even being a noob does not free you from reading the manual. Proxmox, although a very nice and clean solution, is by nature rather complex - as are all virtualization systems that aim at the enterprise level.

Besser nicht! Man kann in einem ZPOOL verschieden große Devices verwenden, aber nicht im selben vdev. Wenn du also z.B. ein raidz2 ZPOOL erstellen willst, dann wird ZFS das nur mit mind. 3 gleich großen Platten machen.

Yes, this can be tricky, if you only have one interface available. What I am always doing is to bind the IP to the vmbr instead of the real interface. Afaik, you can remove the host IP from enp2s0 and attach it to the vmbr0, along with the rest of the IP config (dns, gateway). When you're...

I don't see why this should call for a restart of the PVE host.

Well… your vmbr0 has no network device(s) attached - so the VMs can only communicate among themselves.

Whats the config of your pve hosts's network?

Well… it depends of course. If your users complain about bad performance, than you should probably check that out. Just check-up on a VM and monitor the i/o wait in top. If that is significantly high, than this would surely indicate to issues with the underlying storage. However, what counts...

You aren't running that many VMs on a single spinning HDD, do you? A traditional HDD has by far too few IOPs to satisfy so much I/O demand.

Right… I see… I am running a split-domain installation, where I do have the same domain locally as well as externally. A wildcart cert is of the form *.domain.tld and would cover all hosts or subdomains of domain .tld with one cert. This is, what I am doing, so I only need to deploy one...

So am I and I do have no issues pinging with a packetsize of 9000: root@iceph01-gh79:~# ping -s 9000 iceph02-gh79-vmbr0-osd.jvm.de PING iceph02-gh79-vmbr0-osd.jvm.de (10.11.7.26) 9000(9028) bytes of data. 9008 bytes from iceph02-gh79-vmbr0-osd.jvm.de (10.11.7.26): icmp_seq=1 ttl=64 time=0.599...

Are your switch ports configured for jumbo frames?

If you get a wildcard cert than it will work.

If you want to perform your requests via a DNS challenge, you need to be able to provide a token which is served by your outside domain's DNS server. If you want to secure an internal domain, DNS challenge is out of the question, since LetsEncrypt wouldn't be able to query that.

It would be good though to have the vm configs before doing so and performing the addition of space to your rpool will do that - unless… you do have a good backup of your vm configs, then I'd concurr and re-installed pve as well.

What's a "network device". Other than that, I have been running my DNS on VMs for ages. One could choose to run that in container, which is just as fine. The only thing to keep in mind is that, if the VM server is down for whatever reason, so is your DNS. Maybe you can deploy a RPi as a...

This is really bad, since you will have almost no choice than to provide more space to the ZFS pool, which in your case resides on a partition of the sata DOM and which you will likely be unable to expand. You would somehow need to add additional space to this pool. One possible way would be to...