lmt 3.2.10 displays INACTIVE for most targets
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 77
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I've upgraded from 3.2.7 to 3.2.10 and now all but one OST display the message INACTIVE 0s remaining instead of the current statistics. Only one OST went through recovery and has
status: COMPLETE in recovery_status, all others have INACTIVE, but they are mounted and working fine.
I'm running Lustre 2.10.8.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the upgrade from lmt 3.2.7 to 3.2.10 on Lustre 2.10.8 and compare the affected OSTs with the one showing COMPLETE in recovery_status. Trace how recovery_status is interpreted for mounted, working OSTs; done means current statistics appear instead of INACTIVE 0s remaining.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100