Instructions for building, configuring and running Lustre:
https://wiki.hpdd.intel.com/display/PUB/Building+Lustre+from+Source
and
https://wiki.hpdd.intel.com/display/PUB/Getting+started+with+Lustre.
Instructions for contributing patches for Lustre:
https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes
and
https://wiki.hpdd.intel.com/display/PUB/Using+Gerrit
The Lustre Coding Style Guidelines can be found at:
https://wiki.hpdd.intel.com/display/PUB/Coding+Guidelines
The Lustre Test Script Style Guidelines can be found at:
https://wiki.hpdd.intel.com/display/PUB/Test+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 ../..
John L. Hammond
authored
In ll_file_io_generic() use the position returned in the kiocb to set the returned file position. This ensures that the file position is set correctly after an appending write. Add sanity test_23d() to check that calling lseek() for the current offset returns the correct value in this situation. Lustre-change: https://review.whamcloud.com/32641 Signed-off-by:John L. Hammond <john.hammond@intel.com> Change-Id: Ic76ce49db6e87d5294e18546d5b75a12793aa99c Reviewed-on: https://review.whamcloud.com/32661 Reviewed-by: