Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Commits
7042012e
Commit
7042012e
authored
8 months ago
by
Gitlab Bot
Browse files
Options
Downloads
Plain Diff
Merge branch 'preview' into merge-preview-in-main
parents
16ff20c8
50a49b9b
No related branches found
Branches containing commit
No related tags found
5 merge requests
!1116
Main
,
!1114
Foo
,
!1113
Main
,
!1110
Foobar
,
!1098
Automated merge from preview to main
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
+4
-28
4 additions, 28 deletions
doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
with
4 additions
and
28 deletions
doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
+
4
−
28
View file @
7042012e
# Lustre
## Large Files in /scratch
The data containers in
[
Lustre
](
https://www.lustre.org
)
are called
**object storage targets (OST)**
.
The capacity of one OST is about 21 TB. All files are striped over a certain number of these OSTs.
For small and medium files, the default number is 2. As soon as a file grows above ~1 TB it makes
sense to spread it over a higher number of OSTs, e.g. 16. Once the filesystem is used >75%, the
average space per OST is only 5 GB. So, it is essential to split your larger files so that the
chunks can be saved!
Lets assume you have a directory where you tar your results, e.g.
`/scratch/marie/tar`
. Now, simply
set the stripe count to a higher number in this directory with:
```
console
marie@login$
lfs setstripe
-c
20 /scratch/ws/marie-stripe20/tar
```
!!! note
This does not affect existing files. But all files that **will be created** in this
directory will be distributed over 20 OSTs.
## Good Practices
!!! hint "Avoid accessing metadata information"
...
...
@@ -119,18 +98,15 @@ setstripe getstripe setdirstripe getdirstripe
mkdir rm_entry pool_list find
check osts mdts df
[...]
marie@login lfs help setstripe
```
To get more information on a specific option, enter
`help`
followed by the option of interest:
```
console
marie@login lfs help setstripe
setstripe: To create a file with specified striping/composite layout, or
create/replace the default layout on an existing directory:
usage: setstripe [--component-end|-E <comp_end>
]
[...]
marie@login lfs help df
df: report filesystem disk space usage or inodes usage of each MDS and all OSDs or a batch belonging to a specific pool.
Usage: df [--inodes|-i] [--human-readable|-h] [--lazy|-l]
[--pool|-p <fsname>
[
.<pool>]]
[
path]
```
More comprehensive documentation can be found in the man pages of lfs (
`man lfs`
).
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment