Hi,
FYI
It seems that lustre-client-dkms-2.15.4 is still checking for python2 and does
not install on AlmaLinux 9.3
# dnf --enablerepo=lustre-client install lustre-client lustre-client-dkms
Last metadata expiration check: 0:04:50 ago on Fri Jan 19 11:43:54 2024.
Error:
Problem: conflicting
I have a question about the following comment:
>>> The usual practice is to use RAUD10 for the MDT(s) on "enterprise"
>>> high-endurance SSD, and RAID6 for the OST on "professional" mixed-load SSDs
>>> or "small" (1-2TB at most) "datacenter" HDDs, fronted by failover-servers.
What would be the
- this is an external email **
You should just be able to run the "writeconf" process to regenerate the config
logs. The removed OST will not re-register with the MGS, but all of the other
servers will, so it should be fine.
Cheers, Andreas
On Feb 1, 2023, at 03:48, BALVERS Martin via lust
Hi,
I have a defective OSS with a single OST that I was tying to remove from the
lustre filesystem completely (2.15.1). I was following
https://doc.lustre.org/lustre_manual.xhtml#lustremaint.remove_ost
I had drained the OST and was now using the commands with llog_cancel to remove
the config.
