Need better way to identify filesystem name
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- cli, observability-sre
Research direction
Reproduce the output from /usr/sbin/cerebro-stat -m lmt_mdt and inspect how filesystem names are identified and matched against the expected pattern. The work is done when names such as mds-dc and mds-wan are identified reliably rather than rejected by the current pattern.
Written by the indexing model from the issue text.
Description
One user shared the following output:
/usr/sbin/cerebro-stat -m lmt_mdt
mds01: 1;mds01;2.816180;99.443103;mds-dc;27887837;217526400;742639604;761246852;1116524878;0;0;452067805;0;0;865784;0;0;4402;0;0;26225127;0;0;1170466;0;0;1105360;0;0;1660957;0;0;7832;0;0;2;0;0;8824;0;0;7981;0;0;7419;0;0;6196157;0;0;492;0;0;509;0;0;550165989;0;0;394191904;0;0;149;0;0;442;0;0;0;0;0
mds03: 1;mds03;0.349825;95.817841;mds-wan;57396060;142082048;486786200;497184424;183939442;0;0;86699346;0;0;471;0;0;30;0;0;564650;0;0;109585;0;0;30075;0;0;659897;0;0;232939;0;0;0;0;0;10557;0;0;16344;0;0;7015;0;0;5493522;0;0;48;0;0;56;0;0;1895203;0;0;192098572;0;0;132;0;0;269;0;0;0;0;0
oss19: 1;oss19;0.000000;35.634165;rack5-MDT0000;214167;214238;856668;874872;412;0;0;206;0;0;0;0;0;0;0;0;201;0;0;0;0;0;0;0;0;0;0;0;0;0;0;1;0;0;1;0;0;1;0;0;0;0;0;1537532;0;0;4;0;0;0;0;0;1;0;0;220;0;0;4;0;0;25;0;0;0;0;0
Note the names "mds-dc" and "mds-wan", which do not match the pattern that lmt expects.
- Dominant language
- C
- Stars
- 77
- Forks
- 22
- Avg merge
- 7d 18h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from llnl/lmt
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
fix single key commands consistency and documentationMay be free again @defaziogiancarlo claimed this 1656 days ago, and no pull request is open. Open
-
remove legacy codeMay be free again @defaziogiancarlo claimed this 1657 days ago, and no pull request is open. Open
Similar issues
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Possibly taken @Doomguy-BFG9000 claimed this today. Opengood first issue size:xs skill:native
Difficulty 1/5 Under an hour Newbie friendliness 78/100
SKaiNET-developers/SKaiNET#1358 · 1 comment ·
Maintainers usually reply within 1 day
-
I/O internal correctness medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
libsdl-org/SDL#16539 ·
Maintainers usually reply within 1 day
-
git-workflow task-4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day