Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
Lustre 2.6.0
-
None
-
3
-
14036
Description
When LU-4606 landed it broke Lustre's --with-zfs-devel configure option which was previously landed in LU-3497.
LU-4096 introduces a requirement to link userspace tools against libzfs and is not taking into account the path that --with-zfs-devel may be pointing to.
This landing, unfortunately passes testing on Toro but that is because Toro is masking this bug due to it having had libzfs installed as a system package on it's builders, which we want to avoid on Onyx.
This is because what is actually happening on Toro is that the Lustre build is getting it's headers from the path that --with-zfs-devel points to (which is the ZFS that was built at the same time as Lustre) but is linking against the library that is installed system-wide, which could be mis-matched.
Fortunately at this time, and on this branch they are at least API compatible but that could change on a different branch or as the ZFS API is updated and the system-installed zfs-devel stagnates.
This kind of divergence (between what is being built with Lustre and what is installed on the builders) and the masking of this bug is why zfs-devel should never have been installed as a system package on the builders and why we want to avoid it on Onyx.
Attachments
Issue Links
- is duplicated by
-
LU-5096 Linker cannot find custom libzfs location like it can with header files
- Resolved
- is related to
-
LU-5096 Linker cannot find custom libzfs location like it can with header files
- Resolved
-
LU-5643 Flubbed merging of two patches in change I1d69b64eec1589f63e24f20cc624778a4be2ec60
- Resolved
- is related to
-
LU-4606 Lustre hard codes libzfs.so.1 in lustre/utils/mount_utils_zfs.c
- Resolved