If you are only changing the nid then you do not need to follow the full
writeconf procedure.
See https://doc.lustre.org/lustre_manual.xhtml#lustremaint.changingservernid :
If you need to change only the NID of the MDT or OST, the replace_nids command
can simplify this process. The replace_nids
What version(s) are you using? Do you have an old client and a new-ish server?
Very old client versions will disagree with the MDSes about how to clean up
objects, resulting in orphans.
-Cory
On 10/17/22, 3:44 AM, "lustre-discuss"
wrote:
Thank-you!
-Original Message-
From:
The classical way to put a limit on recovery is to use the recovery_time_soft
and recovery_time_hard mount options.
See the mount.lustre options:
https://doc.lustre.org/lustre_manual.xhtml#idm139974521647280
recovery_time_soft=timeout
Allows timeout seconds for clients to reconnect for
If it is taking too long for targets to sync-up you can tune the activity and
speed things up by adjusting some osp tunables.
First, monitor osp sync_in_progress and destroys_in_flight to see if that’s
what’s going on. Then you can tune up the MDS’s osp’s max_rpcs_in_progress if
necessary.
No, you won’t have MDT interop to worry about in that case.
-Cory
On 2/23/22, 8:44 AM, "Kurt Strosahl" wrote:
We only have a single, combined, mdt-mds... Would that impact it?
From: Spitz, Cory James
Sent: Wednesday, February 23, 2022 9:38 AM
To: Patrick
Kurt,
Also, please be aware of https://jira.whamcloud.com/browse/LU-15177. A version
interop check won’t allow MDT-MDT version skew > 3 minor versions. Note, that
check is just about MDT versions.
-Cory
On 2/21/22, 8:59 PM, "lustre-discuss"
wrote:
Kurt,
The phrasing is a little
What versions do you have on your servers and clients? Do you have some wide
gap in versions? Is your sever very old?
There was a change to the object deletion protocol that you may need to contend
with. It was related to LU-5814. If you don't have an older server then this
is not your
Hello, Megan.
I was curious why you made this comment:
> A general example is a box with lustre-client 2.10.4 is not going to be
> completely happy with a new 2.12.x on the lustre network
In general, I think that the two LTS release are very interoperable. What
incompatibility are you
> lfsck needs to be done with the whole volume offline?
No, in Lustre 2.x lfsck is an online tool.
Per https://doc.lustre.org/lustre_manual.xhtml#idm139675950896912:
Disaster recovery tool: The Lustre file system provides an online distributed
file system check (LFSCK) that can restore
