Skip to content
Snippets Groups Projects
Commit cf43d0d4 authored by Ulf Markwardt's avatar Ulf Markwardt
Browse files

Lustre aus Filesystems genommen

parent 975c9528
No related branches found
No related tags found
3 merge requests!322Merge preview into main,!319Merge preview into main,!223Filesystems.md
...@@ -86,23 +86,6 @@ In case a project is above it's limits please ... ...@@ -86,23 +86,6 @@ In case a project is above it's limits please ...
| `BeeGFS` | `/beegfs/global0` | 232 TB | global | No | Only accessible via **todo link: workspaces - WorkSpaces**. Fastest available file system, only for large parallel applications running with millions of small I/O operations | | `BeeGFS` | `/beegfs/global0` | 232 TB | global | No | Only accessible via **todo link: workspaces - WorkSpaces**. Fastest available file system, only for large parallel applications running with millions of small I/O operations |
| `ext4` | `/tmp` | 95.0 GB | local | No | is cleaned up after the job automatically | | `ext4` | `/tmp` | 95.0 GB | local | No | is cleaned up after the job automatically |
### Large Files in /scratch
The data containers in Lustre 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, eg. 16. Once the file system 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 dierctory where you tar your results, e.g. `/scratch/mark/tar`. Now, simply
set the stripe count to a higher number in this directory with:
```Bash
lfs setstripe -c 20 /scratch/ws/mark-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.
## Warm Archive ## Warm Archive
...@@ -167,44 +150,7 @@ output. ...@@ -167,44 +150,7 @@ output.
We do **not recommend** the usage of the "du"-command for this purpose. It is able to cause issues We do **not recommend** the usage of the "du"-command for this purpose. It is able to cause issues
for other users, while reading data from the filesystem. for other users, while reading data from the filesystem.
### Lustre File System
These commands work for `/scratch` and `/ssd`.
#### Listing Disk Usages per OST and MDT
```Bash
lfs quota -h -u username /path/to/my/data
```
It is possible to display the usage on each OST by adding the "-v"-parameter.
#### Listing space usage per OST and MDT
```Bash
lfs df -h /path/to/my/data
```
#### Listing inode usage for an specific path
```Bash
lfs df -i /path/to/my/data
```
#### Listing OSTs
```Bash
lfs osts /path/to/my/data
```
#### View striping information
```Bash
lfs getstripe myfile
lfs getstripe -d mydirectory
```
The `-d`-parameter will also display striping for all files in the directory
### BeeGFS ### BeeGFS
......
# Lustre File System(s)
### Large Files in /scratch
The data containers in Lustre 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, eg. 16. Once the file system 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 dierctory where you tar your results, e.g. `/scratch/mark/tar`. Now, simply
set the stripe count to a higher number in this directory with:
```Bash
lfs setstripe -c 20 /scratch/ws/mark-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.
## Useful Commands for Lustre
These commands work for `/scratch` and `/ssd`.
### Listing Disk Usages per OST and MDT
```Bash
lfs quota -h -u username /path/to/my/data
```
It is possible to display the usage on each OST by adding the "-v"-parameter.
### Listing space usage per OST and MDT
```Bash
lfs df -h /path/to/my/data
```
### Listing inode usage for an specific path
```Bash
lfs df -i /path/to/my/data
```
### Listing OSTs
```Bash
lfs osts /path/to/my/data
```
### View striping information
```Bash
lfs getstripe myfile
lfs getstripe -d mydirectory
```
The `-d`-parameter will also display striping for all files in the directory
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment