https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-5091 Lustre <p>When <a href="https://jira.whamcloud.com/browse/LU-4606" title="Lustre hard codes libzfs.so.1 in lustre/utils/mount_utils_zfs.c" class="issue-link" data-issue-key="LU-4606"><del>LU-4606</del></a> landed it broke Lustre's <tt>--with-zfs-devel</tt> <tt>configure</tt> option which was previously landed in <a href="https://jira.whamcloud.com/browse/LU-3497" title="Lustre build system hardcoded to using ZFS development headers in /usr/include only. " class="issue-link" data-issue-key="LU-3497"><del>LU-3497</del></a>.</p> <p><a href="https://jira.whamcloud.com/browse/LU-4096" title="Do not allocate large buffer for readdir rpc in case of a small directory" class="issue-link" data-issue-key="LU-4096"><del>LU-4096</del></a> introduces a requirement to link userspace tools against <tt>libzfs</tt> and is not taking into account the path that <tt>--with-zfs-devel</tt> may be pointing to.</p> <p>This landing, unfortunately passes testing on Toro but that is because Toro is masking this bug due to it having had <tt>libzfs</tt> installed as a system package on it's builders, which we want to avoid on Onyx.</p> <p>This is because what is actually happening on Toro is that the Lustre build is getting it's headers from the path that <tt>--with-zfs-devel</tt> 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.</p> <p>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 <tt>zfs-devel</tt> stagnates.</p> <p>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 <tt>zfs-devel</tt> should never have been installed as a system package on the builders and why we want to avoid it on Onyx.</p> LU-5091

LU-4606 breaks --with-zfs-devel option

Bug Blocker Resolved Fixed Nathaniel Clark Brian Murrell Tue, 20 May 2014 18:41:45 +0000 Fri, 19 Sep 2014 22:36:15 +0000 Wed, 28 May 2014 17:35:46 +0000 Lustre 2.6.0 Lustre 2.6.0 0 4 <p>Ran into this issue as well. To tired to make a patch right now tho.</p> <p><a href="http://review.whamcloud.com/10401" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10401</a></p> <p>Since all the builders currently have zfs RPMs installed on them, how do we test that this actually fixes the issue.</p> <p>Oh...<a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=brian" class="user-hover" rel="brian">brian</a>: if this builds on Onyx, then we're good, right?</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=joshua" class="user-hover" rel="joshua">joshua</a>: Yep.</p> <blockquote> <p><a href="http://review.whamcloud.com/10401" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10401</a></p></blockquote> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=utopiabound" class="user-hover" rel="utopiabound">utopiabound</a>: Note that in the above patch, in lbuild you will need to arrange for the <tt>zfs</tt> RPM to be unpacked with <tt>rpm2cpio | cpio</tt> in addition to the existing unpacking of the <tt>zfs-devel</tt> RPM.</p> <p>This is because the <tt>zfs-devel</tt> RPM doesn't contain any actual libraries but only contains the unversioned library symlinks pointing at the libraries that are installed with the <tt>zfs</tt> RPM.</p> <p>Landed in b2659030edb7d34c91430ff924bab23881b6c230.</p> Duplicate LU-5096 Related LU-4606 LU-5096 LU-5643 Development Rank 1|hzwmtb: Rank (Obsolete) 14036 Severity