hpc / hpc/mpifileutils

Determine underlying file systems

Open
#27 0 comments 0 reactions 1 assignee View on GitHub

@dinatale2 is already working on this.

Since Oct 14, 2016.

wish list
Dominant language
C
Stars
200
Forks
85
Avg merge
3d 21h
Merged PRs (30d)
2

Description

Different underlying file systems can require different approaches, especially at scale. We need a way to identify the underlying file system as well as its properties (e.g., default stripe size and width). This will enable optimizations specific to each file system.

For example, we'd like to know whether a target file system is Lustre, GPFS, or NFS, and in the case of Lustre, we'd like to know how many object servers it has. This info will help to maximize parallelism and determine file chunking such that we can mitigate Lustre lock thrashing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.