Skip to content

openai/lustre

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code
This branch is 3050 commits behind Cray:master.

Latest commit

0 should be returned if no error is found in mdt_path_current(),
otherwise, the non-zero value will be treated as an error in
mdc_ioc_fid2path() and null will be returned by "lfs fid2path".

sanity.sh test_226c is added to verify this patch.

Signed-off-by: Emoly Liu <emoly@whamcloud.com>
Change-Id: I1c10b023da9bbbb908dfb691fcea6e84ced67a8d
Reviewed-on: https://review.whamcloud.com/39688
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
6a3599a

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
rpm
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Many resources for using, configuring, and troubleshooting Lustre are at:
    http://wiki.lustre.org/

The low-volume list for announcements of new releases is at:
    http://lists.lustre.org/listinfo.cgi/lustre-announce-lustre.org
The generic Lustre discussion mailing list is available at:
    http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
The Lustre developer mailing list is at:
    http://lists.lustre.org/pipermail/lustre-devel-lustre.org

Instructions for building, configuring and running Lustre:
    http://wiki.lustre.org/Compiling_Lustre
and
    https://wiki.whamcloud.com/display/PUB/Getting+started+with+Lustre.

Instructions for contributing patches for Lustre:
    http://wiki.lustre.org/Submitting_Changes
and
    http://wiki.lustre.org/Using_Gerrit

The Lustre Coding Style Guidelines can be found at:
    http://wiki.lustre.org/Lustre_Coding_Style_Guidelines

The Lustre Test Script Style Guidelines can be found at:
    http://wiki.lustre.org/Lustre_Script_Coding_Style

In order to improve the quality of patches submitted to the Lustre tree,
it is possible to automatically check every patch and commit against the
Lustre Coding Guidelines.  To do this, run in the top-level lustre/ tree:

    cd .git/hooks
    ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./
    cd ../..

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 79.5%
  • Shell 15.0%
  • Roff 1.6%
  • Perl 1.6%
  • M4 1.0%
  • Python 0.6%
  • Other 0.7%