Hey J-F,
we invest a lot of time and resources to keep our kernel module compatible
with all major distributions, but supporting us by buying a support
contract is always appreciated and helps us allocate more resources to be
able to support new kernel and OS versions even faster ;D.
The kernel had a pretty substantial API change in page handling starting
from version 5.18 that mandated some client module modifications on our
end. Some of those changes seem to have made their way into RedHat 9.2,
which hadn't even been released when we released version 7.3.3.
It is always a good idea to check our release notes ([1] for 7.3.3) before
upgrading operating systems. We have a detailed list of supported operating
systems and kernels we run build tests for. If the OS version (including
minor) is not included in that list, especially for RedHat based
distributions, chances are high that there will be issues with the build.
All other major distributions keep their kernels pretty stable and
therefore aren't affected as much and give us more time to prepare, which
is why we have some code that is currently in testing to support kernels up
to version 6.1 (Debian 12). If all goes well, that code will be released
with our next maintenance releases, very shortly after the Debian 12
release, and also add support for RHEL/Rocky/Alma 9.2.
Best regards and have a good weekend
- Philipp
[1]
https://doc.beegfs.io/7.3.3/release_notes.html
*
jeanfranco...@gmail.com <
jeanfranco...@gmail.com> [230609 03:19]:
> Hello,
>
> *Same problem here, with AlmaLinux 9.2:*
>
> [root@beegfs01 sock]# uname -a
> Linux
beegfs01.jeffcourteau.int 5.14.0-284.11.1.el9_2.x86_64 #1 SMP
> PREEMPT_DYNAMIC Tue May 9 05:49:00 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
>
> *I get the exact same errors. Full startup log here:*
> *Here are my build args from /etc/beegfs/beegfs-client-automount.conf. I
> disable RDMA support, I have the most basic virtual machines setup in KVM:*
> buildArgs=-j8 BEEGFS_NO_RDMA=1
>
>
> *If I let RDMA support enabled, the errors change (Remove BEEGFS_NO_RDMA
> arg), but still, compile doesn't succeed:*
> > CC [M] */var/lib/dkms/beegfs/7.3.3/build/build/*../source/app/config/Config.o
> >
> > */var/lib/dkms/beegfs/7.3.3/build/build/*../source/filesystem/FhgfsOpsFile.c:156:5:
> > error: ‘struct address_space_operations’ has no member named ‘readpages’;
> > did you mean ‘readpage’?
> > 156 | .readpages = FhgfsOpsPages_readpages,
> > | ^~~~~~~~~
> > | readpage
> > */var/lib/dkms/beegfs/7.3.3/build/build/*../source/filesystem/FhgfsOpsFile.c:156:22:
> > error: initialization of ‘int (*)(struct address_space *, struct
> > writeback_control *)’ from incompatible pointer type ‘int (*)(struct file
> > *, struct address_space *, struct list_head *, unsigned int)’
> > [-Werror=incompatible-pointer-types]
> > 156 | .readpages = FhgfsOpsPages_readpages,
> > | ^~~~~~~~~~~~~~~~~~~~~~~
> >
> > [...]
> >
> > Did anyone run into the same issue and maybe knows a way around?
> >
> > I am also curious if there are any best practices when weighing off
> > recommended kernel updates against waiting for updates to projects that
> > build against the kernel (e.g. beegfs-client).
> >
> > Cheers
> > Martin Errenst
> >
>
> --
> You received this message because you are subscribed to the Google Groups "beegfs-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
fhgfs-user+...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/fhgfs-user/2191421c-5e8a-4a03-acc6-168273c42d05n%40googlegroups.com.
--
Philipp Falk | Head of Engineering | m:
philip...@thinkparq.com
ThinkParQ GmbH | Trippstadter Strasse 113 | 67663 Kaiserslautern | Germany
CEO: Frank Herold | COB: Dr. Franz-Josef Pfreundt | Registered: Amtsgericht Kaiserslautern HRB 31565 I VAT-ID-No.:DE 292001792
Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information.