Unusually low number of exports for 2.12 file systems
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 77
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Our latest file system is 2.12.2 based, and after compiling the latest lmt to work with it, we noticed something unusual. We knew approximately how many clients had this file system mounted, but the export count shown in ltop was significantly lower. We also noticed after upgrading all our clients to 2.12.2 that the export counts on our 2.10.5 file systems were also lower, but not as low as on our new 2.12.2 system.
After stopping all jobs on our 2.12.2 file system for another reason, we noticed that the export counts went down to 2 or 3. More research led us to this new 2.12 feature: https://jira.whamcloud.com/browse/LU-7236. Apparently Lustre 2.12 has a "connections on demand" feature so the number of exports now equals the number of "active" clients. In the past, we used this as an indicator of how many clients were mounted.
In retrospect it makes sense, but it took us a while to figure out what was going on. I don't know if it makes sense to do anything to highlight this difference from the ltop side, but if nothing else this issue can be closed and serve as a notice to future 2.12 users explaining the cause for the new ltop behavior.
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 reviewing how ltop presents export counts and the issue's description of Lustre 2.12 connections-on-demand behavior. Confirm whether the project has user documentation or UI guidance that explains the changed meaning of exports; done means providing a clearly scoped explanatory update, if one is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability-sre
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100