Karsten Weiss

@stapelberg By adding a 2nd virtual serial port I was finally able to capture the full output of the (unsuccessful) virtual SCSI hdisk boot into a file (with `loglevel=7`!): [...

FWIW: The older Distri version "jackherer" boots from a virtual SCSI hdisk in VMware Fusion.

FWIW: I've just tested this successfully with k3s v1.22.6+k3s1 (stable channel). I.e. start k3s with `--etcd-expose-metrics=true` and then configure the local kube-prometheus-stack-32.2.1 `values.yaml` to a) enable `kubeEtcd` b) list the...

FWIW: I'm working on some other fixes and also just noticed occasional test failures in `TestServerInterceptorSuite` on my local system (8-core, otherwise idle): ``` $ go test -run=TestServerInterceptorSuite --- FAIL:...

Which installed k3s version did you try to upgrade?

May I also suggest that deprecated linters should be removed from the various `--presets` sets? Example: ``` $ golangci-lint run -p bugs WARN [runner] The linter 'scopelint' is deprecated (since...

We also had a similar case recently: A **single** failing SSD of a ZFS-based Lustre metadata server was causing the entire zpool to get SUSPENDED by the MMP timeout (and...

@tonyhutter FWIW: I've just updated a zfs 2.1.5 Rocky Linux 8.6 system from kernel-4.18.0-372.19.1.el8_6.x86_64 to kernel-4.18.0-372.26.1.el8_6.x86_64 using dkms-3.0.7 (_without_ updating zfs!). I got the same output as you i.e. it...

@tonyhutter Interesting. FWIW I was using zfs-2.1.5-1 as a starting point. Which dkms were you using? (dkms-3.0.7-1.el8.noarch here). I assume your `dkms status` output shows no warning? I've just verified:...

Also, checking the bit sizes of the configured SSH **user** keys (e.g. RSA >= 2048 bit) would be another useful client-side check.