Search results

No,didnt need that on my end.

here is how i do it in ex2200: ge-0/0/21 { description SP1-data; unit 0 { family ethernet-switching { interface-mode trunk; vlan { members [ Server-Vlan Host-Vlan Voice-Vlan Wifi-Vlan ];

I had similar problem with megaraid_sas, the zfs 1 boot disks couldnt write to it if the machine load was high. Once i've shutdown the Vms on it, the kernel upgrade or proxmox-boot-tool would run okay. this was supermicro.

Usually very high load shows problems with storage, eg disks cannot write fast enough. First look at disks.

I do it all the time for my customers, but what WIndows version do you have?

What is the use-case for SaunaFS in Proxmox, for image storage like CephFS or do you run VM's on it? Since you are using sata drives, did you run some fio tests or similar to compare the perf to ceph?

In that case best you can do is use zfs on both nodes, and pve-zsync.

If you are using hardware raid, then you format it as lvm-thin by default(i usually do). Then you create Splunk on top of that. But why raid5 instead of raid10, much more IOPS you get from that.

CEPH is only real HA that is best-in-class supported in Proxmox, so i would always choose that.

i'm working with 5 nodes and EC pool, so i would say atlest 5 but maybe it doesnt make that much sense.

If you machine is debian 13 than okay, why not.

Tested on 3 machines, bcachefs also works :)

bcachefs works with current 6.14 kernel, i tested it a few days ago. But didn't get that good performance from it.

I would just wait for a week until proxmox publishes 6.17 test.

So spread you db/wal onto 2+ disks.

I don't get why you need LLM to check sha.

In the earlier days ,usually it was recommended 1 ssd or nvme onto 4 hdds for wal.

Cephfs is not meant for nas, like small files,so don't do that.

Sata drives are okay for OS,just buy enterprise ones.

There is now zfs rewrite,which you can use for rebalance