Skip to content
Snippets Groups Projects
user avatar
Nathaniel Clark authored
Make mount/mkfs/tunefs functionality a per backing FSTYPE shared
object that is loadable, and seperately buildable and installable
in the appropriate lustre-osd-FSTYPE rpm.

For ZFS this allows the shared object to be directly linked to libzfs
and thus remove the hardcoding of a libzfs.so version in the lustre
source. This also has the benefit of making lustre-osd-zfs explicitly
requires libzfs (which it needs to do mount/mkfs operations).

Adjust build system to allow building of loadable module.  Including
requiering libtool as part of the build.

Signed-off-by: default avatarNathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I8fc0f41161dc08405c1f951f12e675f364ff62c3
Reviewed-on: http://review.whamcloud.com/10193


Tested-by: Jenkins
Reviewed-by: default avatarDmitry Eremin <dmitry.eremin@intel.com>
Tested-by: default avatarMaloo <hpdd-maloo@intel.com>
Reviewed-by: default avatarAlex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: default avatarOleg Drokin <oleg.drokin@intel.com>
3e8c354c
History
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:

    cp build/{prepare-,}commit-msg .git/hooks/