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 ../..
Bobi Jam
authored
* obd_fid_alloc() could possibly start a nested transaction, which would reset the OI cache. So we add a osd_thread_info::oti_ins_cache_depth to prevent clearing OI cache in the nested trnasaction. * Add more debug mesages in osd_idc_find_or_init()/ osd_idc_find_and_init() Test-Parameters: alwaysuploadlogs envdefinitions=PTLDEBUG=-1 testlist=sanity-pfl ostfilesystemtype=zfs mdtfilesystemtype=zfs mdscount=2 mdtcount=4 Signed-off-by:Bobi Jam <bobijam.xu@intel.com> Change-Id: Id75fd1787ffc0f47bbf110d460f23db6c34670da Reviewed-on: https://review.whamcloud.com/31268 Reviewed-by: