Add lfs migrate examples to storage guide
#297
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… setstripe recommendation
|
preview available: https://docs.tds.cscs.ch/297 |
|
preview available: https://docs.tds.cscs.ch/297 |
bcumming
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the
lfs migraterecommendation/example that was removed along with the Gordon-Bell guide (#240).This also adds an example to recursively update all files in a directory (finding files using
lfs find).@mpasserini can you or someone else from the storage team comment if you think these are ok recommendations. For example:
xargs -Pto migrate files in parallel (the example is currently sequential which can be slow, but I'm not sure if doing a parallellfs migrateadds unnecessarily high load on lustre)?Note that I changed the short options (
-c/-S/-E) to long options as I find that it's easier to follow for someone like me who doesn't know the options by heart. However, the commands do end up being longer (wider than the regular page, and require scrolling), and I'm happy to change that back (it's not the important part of this PR).I'm not attempting to move or restructure the storage guide otherwise.
Link to generated docs:
https://docs.tds.cscs.ch/297/guides/storage/#lustre-tuning