The mailing list is not a great place to file bug reports. Jira would be 
better, and including a patch would be best. :-)

Cheers, Andreas

> On Jun 24, 2022, at 08:24, Thomas Roth via lustre-discuss 
> <lustre-discuss@lists.lustre.org> wrote:
> 
> Since it seems I have now managed to create the modules, I'd like to record 
> that here:
> 
> 1. Install system w AlmaLinux 8.5 -> kernel 4.18.0-348.23.1
> 2. Install packages from Whamcloud (lustre-2.15.0/el8.5.2111/server/): 
> lustre, kmod-lustre, kmod-lustre-osd-ldiskfs -> fails due to the discussed 
> 'unknown symbols', cf. https://jira.whamcloud.com/browse/LU-15962
> 3. Install the correspoding dkms-packages -> fails, reason not clear
> 4. Go to the remnant /var/lib/dkms/lustre-ldiskfs/2.15.0/build, run configure 
> with '--with-o2ib=/usr/src/kernels/4.18.0-348.23.1.el8_5.x86_64' (that's were 
> the kernel-devel + the extfs sources ended up in this case)
> 5. 'make rpms' now fails with
> 
> > make[4]: Entering directory 
> > '/var/lib/dkms/lustre-ldiskfs/2.15.0/build/lustre/utils' 
> > ... 
> > In file included from liblustreapi.c:83: 
> > lstddef.h:306:22: error: static declaration of ‘copy_file_range’ follows 
> > non-static declaration 
> > │static inline loff_t copy_file_range(int fd_in, loff_t *off_in, int 
> > fd_out, 
> 
> 
> This was already reported last year, e.g. 
> https://www.mail-archive.com/lustre-discuss@lists.lustre.org/msg16822.html
> The workaround is also given there: the configure command line has 
> '--disable-utils' (by default), somehow this makes make go to 'utils' and 
> fail.
> 
> 6. Repeat 'configure with the '-with-o2ib=/usr/src/kernels...' and without 
> '--disable-utils'
> 7. 'make rpms' yields some installable kmod packages, the contained modules 
> can be loaded (I haven't setup the file system yet).
> 
> 
> Cheers,
> Thomas
> 
> 
> PS: My rather spartan Alma-installation needed in addition 'dnf install'
> > kernel-headers-4.18.0-348.23.1.el8_5.x86_64 
> > kernel-devel-4.18.0-348.23.1.el8_5.x86_64 dkms
> > kernel-4.18.0-348.23.1.el8_5.src
> > e2fsprogs-devel rpm-build kernel-rpm-macros  kernel-abi-whitelists 
> > libselinux-devel libtool
> 
> 
> 
> 
> 
> 
>> On 6/22/22 21:08, Jian Yu wrote:
>> Hi Thomas,
>> The issue is being fixed in https://jira.whamcloud.com/browse/LU-15962.
>> A workaround is to build Lustre with "--with-o2ib=<path>" configure option.
>> The <path> is where in-kernel Module.symvers is located.
>> --
>> Best regards,
>> Jian Yu
>>  -----Original Message-----
>> From: lustre-discuss <lustre-discuss-boun...@lists.lustre.org> on behalf of 
>> Thomas Roth via lustre-discuss <lustre-discuss@lists.lustre.org>
>> Reply-To: Thomas Roth <t.r...@gsi.de>
>> Date: Wednesday, June 22, 2022 at 10:32 AM
>> To: Andreas Dilger <adil...@whamcloud.com>
>> Cc: lustre-discuss <lustre-discuss@lists.lustre.org>
>> Subject: Re: [lustre-discuss] Installing 2.15 on rhel 8.5 fails
>>     Hmm, but we are using the in-kernel OFED, so this makes these messages 
>> all the more mysterious.
>>     Regards,
>>     Thomas
>>          On 22/06/2022 19.12, Andreas Dilger wrote:
>>     > On Jun 22, 2022, at 10:40, Thomas Roth via lustre-discuss 
>> <lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>> 
>> wrote:
>>     >
>>     > my rhel8 system is actually an Alma Linux 8.5 installation, this is 
>> the first time the compatiblity to an alleged rhel8.5 software fails...
>>     >
>>     >
>>     > The system is running kernel '4.18.0-348.2.1.el8_5'
>>     > This version string can also be found in the package names in
>>     > 
>> https://downloads.whamcloud.com/public/lustre/lustre-2.15.0/el8.5.2111/server/RPMS/x86_64
>>     > - this is usually a good sign.
>>     >
>>     > However, installation of kmod-lustre-2.15.0-1.el8 yields the well 
>> known "depmod: WARNINGs", like
>>     >> 
>> /lib/modules/4.18.0-348.2.1.el8_lustre.x86_64/extra/lustre/net/ko2iblnd.ko 
>> needs unknown symbol __ib_alloc_pd
>>     >
>>     >
>>     > The kernel from 
>> downloads.whamcloud.com/public/lustre/lustre-2.15.0/el8.5.2111/server/RPMS/x86_64
>>  identifies itself as "CentOS" and does not want to boot - no option either.
>>     >
>>     >
>>     > Any hints how to proceed?
>>     >
>>     > The ko2iblnd module is built against the in-kernel OFED, so if you are 
>> using MOFED you will need to rebuild the kernel modules themselves.  If you 
>> don't use IB at all you can ignore these depmod messages.
>>     >
>>     > Cheers, Andreas
>>     > --
>>     > Andreas Dilger
>>     > Lustre Principal Architect
>>     > Whamcloud
>>     >
>>                                             --
>>     --------------------------------------------------------------------
>>     Thomas Roth
>>     Department: Informationstechnologie
>>               GSI Helmholtzzentrum für Schwerionenforschung GmbH
>>     Planckstraße 1, 64291 Darmstadt, Germany, www.gsi.de
>>          Commercial Register / Handelsregister: Amtsgericht Darmstadt, HRB 
>> 1528
>>     Managing Directors / Geschäftsführung:
>>     Professor Dr. Paolo Giubellino, Dr. Ulrich Breuer, Jörg Blaurock
>>     Chairman of the Supervisory Board / Vorsitzender des GSI-Aufsichtsrats:
>>     State Secretary / Staatssekretär Dr. Volkmar Dietz
>>          _______________________________________________
>>     lustre-discuss mailing list
>>     lustre-discuss@lists.lustre.org
>>     http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>>     
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to