Closed JulianKunkel closed 3 years ago
Just a feedback on this fix: YES it works as envisioned. (although - its practical usage is a bit tricky)
Here just some more detail - why this is required:
The E1000-Lustre-MDSs do support DNE-phase2 (striped dirs) The problem is only, that due to the file-naming - ldiskfs doesn't allow me, to create more than ~8mill files/dir. (see for a more detailed explanation: https://github.com/IO500/io500/issues/15 --- issue-#15) S O - with let's say 2 dirstripes - we can then have ~16 mill files in that directory. But - just with the right node-count - I get around 120k file/creates/sec The math then for '-n' and '-I' is:
Again - the '-I=X' is required to not run out of file-entries in a shared dir. Using this option - does not work with stonewalling (it only does 1 dir_loop if stonewalled). Turning off stonewalling - requires this manual calculation - to not over-create too many files. (too many files like 48m instead of 36m - will penalize your find score quite a lot)
In general - the proposed fix worked for me fine.
Thanks for the extensive description of the situation.
You could enable the large_dir feature for ldiskfs, which fixes the directory entry limit.
changing to enable large_dir was what was required previously. What is the motivation for changing this policy.
After a discussion with the board: I will extend the patch to mark the submission automatically as invalid and show this in the options.
The respective change is made.
Note this is only allowed if needed and the committee approves.