[LU-266] Need a better, automated way to recover from failures that require LAST_ID recovery

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Affects Version/s: Lustre 2.0.0, Lustre 2.1.0, Lustre 1.8.6
• Environment: Linux and Lustre
• Bugzilla ID: 22,734
• Assignee: Peter Jones
• Reporter: John Salinas (Inactive)

Description

We continue to see issues where hardware failures create problems on the filesystem that require LAST_ID recovery. While there is a manual procedure to do this it is unnecessarily arduous, especially for the number of times that we continue to have to do this.

Bug 22734 details one possible automated solution to this. It is possible there are other way to handle this and we would be open to exploring them as long as we can arrive at something that is as simple (or even simpiler) to run to recover quickly from this situation.

Issue Links

• is related to: LU-14 live replacement of OST
• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA