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-2882 Lustre <p>after rebaising to last master i see build without zfs libraries broken.</p> <p>RPM build errors:<br/> File not found: /root/rpmbuild/BUILDROOT/lustre-2.3.61-2.6.32_279.5.2.lustre_g91ba9d3.x86_64/lib/modules/2.6.32-279.5.2.lustre/updates/kernel/fs/lustre/osd_zfs.ko</p> <p>quick look into spec file say - build_lustre_osd_zfs now is '1' but that is don't checked in build requirements and produced bug in at final phase as osd_zfs isn't build.</p> <p>i know about workaround with --define "build_lustre_osd_zfs 0" with rpmbuild -tb, but suggest to add some checks for it.<br/> may be via autogenerated package list.</p> clean rhel6 build env. LU-2882

lustre build broken with no zfs libraries installed

Bug Blocker Resolved Fixed Bruno Faccini Alexey Lyashkov MB Wed, 27 Feb 2013 04:20:14 +0000 Mon, 18 Mar 2013 23:18:41 +0000 Mon, 18 Mar 2013 23:18:41 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>Hello Alexey,<br/> Can you better detail me with the commands/setup you use for your build ?<br/> It will help me to find any holes in the add-ons for these OSD RPMs in the spec file.</p> <p>Bruno, it seems what shadow is doing is just<br/> rpm -tb lustre.spc on a system with no zfs/spl stuff installed.<br/> Please try that and see if it fails for you, and if so, please see if you can fix it.</p> <p>Ho thank's Oleg I see, he uses "rpmbuild -tb" on a source tar-ball. Yes, this may be the trick, because changes from <a href="https://jira.whamcloud.com/browse/LU-2391" title="warning messages for missing symbols when lustre-modules::osd_zfs.ko installed on a system without zfs-modules installed" class="issue-link" data-issue-key="LU-2391"><del>LU-2391</del></a> have only been exposed vs local builds as described on the WiKi and Hudson/Jenkins (aka "lbuild") builds.</p> <p>And, particularly, the "lbuild" ones are using "rpmbuild -tb" command but with a lot of spec-file variables pre-setting (like %configure !!...) mainly coming from "autoconf/configure", and I am afraid that a simple "rpmbuild -tb" will only get embryonic configure infos that will not allow to decide if ZFS is installed or not.</p> <p>I will try to revert the default value from 1 to 0 for build_lustre_osd_zfs/build_lustre_osd_ldiskfs, and see if it fixes.</p> <p>But back on my previous comment about the different ways to build Lustre, is this "rpmbuild -tb lustre-source-tarball" a usual one ??</p> <p>Also, are there others known ?</p> <p>Since I am not able to build simply with a simple/only "rpmbuild -tb lustre-source-tarball" command (ldiskfs_* symbols undefined references in osd_*() functions from lustre/utils/mount_utils.c, so again I may need some details on commands/sequence used), I am not sure about the fix, but since my local/Wiki-like builds tests with it have been successful, let's have a try with patch at <a href="http://review.whamcloud.com/5661" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5661</a> on Hudson/Jenkins side.</p> <p>Hello Alexey,<br/> Can you re-try your builds when running with my patch ?<br/> Thank's in advance for your help and answer.</p> <p>Hi Bruno,</p> <p>sure. </p> <p>ps. I think patch good after quick look into. but let be run test build.</p> <p>Verified - with patch i able to build packages correctly.</p> <p>Cool! <br/> Thank's again for you help and tests. <br/> I had to re-run 1st auto-tests due to some weird issues, if successful I will then ask for patch to be landed.</p> <p>Landed for 2.4</p> Development Rank 1|hzvjz3: Rank (Obsolete) 6958 Severity