Search results

I wasn't able to, tried `mds_dir_max_commit_size` with and without fail, that's it. Rewrote alert, so it excludes TRIM error and disabled old SAMBA-CTDB cluster + some other clients, longevity of error reduced a little bit. Saw some messages about increasing mds memory, but didn't try and I...

Updated as well, 0 issues during process. Finally RGW IAM present and S3 bucket policies working. However, I'm facing `1 MDSs behind on trimming` warning randomly. Tried some workarounds and now it is persistently grows 700+/128 segments. Might be the fact that I have only 1 slow HDD OSD per...

Yep, can't upgrade to this build. Unexpected tbh, didn't think they'll make TPM for VMs mandatory before 2022-2023.

I guess something is changed in 7.0 (maybe in latest builds of 6.x), got the same issue. Because it's a homelab and I was lazy, turned off node for like half a day, then decided to finally remove it from corosync and received same problem. Manual removal of folders worked.

Sorry for necroing as well. Your solution worked just fine, until Proxmox 6.2. I'm not using my machine as 24/7 server, I'm turning it off for a night. For some reason, after 6.2, efi on that small virtio disk started to rewrite every reboot/power off. Due to this, I was forced to find a...