[lustre-discuss] Fwd: Patch of Lustre-2.16.1 to Linux kernel 6.12.57

Tue Dec 23 08:51:24 PST 2025

Sorry, I should reply this message to the lustre-disscuss mailing list. So
here I forwarded my reply.

Best Regards,
T.H.Hsieh

---------- Forwarded message ---------
寄件者： Tung-Han Hsieh <tunghan.hsieh at gmail.com>
Date: 2025年12月24日週三 上午12:48
Subject: Re: [lustre-discuss] Patch of Lustre-2.16.1 to Linux kernel 6.12.57
To: Shaun Tancheff <shaun.tancheff at hpe.com>

Dear Tancheff,

Thanks very much for your great information. I have tried to build
lustre-2.17-rc2 with Linux kernel-6.12.57. It works. But during test, there
is a strange problem when using "root" account to create directory in
Lustre partition:

(in root account)
(<mds> and <oss> installed Lustre-2.15.3)
# mount -t lustre -o flock <mds>@tcp:/chome /mnt
# cd /mnt
# mkdir tmpdir
# ls
ls: cannot open directory '.': No such file or directory

Then, if I leave the /mnt directory, and enter /mnt again, everything looks
normal. "ls" command is OK, and the /mnt/tmpdir/ directory is created
correctly. There is no such problem in normal user accounts. Since this
testing machine is in a cluster environment, all the normal user account
was created in the head node (not in the node of testing machine). The head
node was configured as a ypserv server, to export normal user information
to all the file servers (including <mds>, <oss>, etc), and all the
computing nodes (including this testing machine).

For my patched Lustre-2.16.1, it also has this problem.

Currently it is not clear how to fix it. Probably Lustre-2.15.3 installed
in the Lustre servers should be upgraded ?

Best Regards,
T.H.Hsieh

Shaun Tancheff via lustre-discuss <lustre-discuss at lists.lustre.org> 於
2025年12月22日週一 上午9:05寫道：

> On 12/20/25 11:08, Tung-Han Hsieh via lustre-discuss wrote:
> > Greetings,
> >
> > Recently we were requested to install Lustre client to a new machine,
> > installed Debian-13.2 (trixie), with Linux kernel 6.12.57. We install
> > it from compiling the source code. During installation, we encountered
> > a lot of compiling errors, due to changes of kernel API from version
> > 5.X.X to 6.12.X. We struggled quite a lot to update the code of
> > Lustre, and finally came out a patch, as shown in the attachment. I
> > would like to submit this patch to the Lustre developer team for
> > review and test, and finally being committed to the future versions of
> > Lustre. This is very important, because as newer machines shipped, we
> > are forced to install newer versions of Linux OS, and Linux kernel. We
> > hope that Lustre file system could work well in these new environments.
> >
> The patch does not look too problematic, however you should be aware
> that Lustre 2.17-rc2 is currently building fine with 6.15, not sure what
> the state of back ports of kernel support are for Lustre 2.16.
>
> FWIW kernel support for 6.16 and 6.17 are enqueue and 6.18 is
> essentially done awaiting the new fs mount API changes James has done (I
> have not yet had a chance to test them together since I am traveling).
>
> > The steps of compiling Lustre in our new machine is following:
> >
> > 1. Use "apt install" to install necessary code building packages, such
> > as build-essential, gcc,
> >     make, autoconf,
> >
> libyaml-dev, uuid-dev, libblkid-dev, libnl-3-dev, libudev-dev, libkeyutils-dev,
>
> >
> >     libmount-dev, python3-dev, libnl-genl-3-dev, libtool, ...., etc.
> >
> > 2. Install the kernel source, which is the version of the current
> > running kernel:
> >     apt install linux-headers-6.12.57+deb13-amd64
> >
> > 3. Download Lustre source 2.16.1 (the newest version we have found),
> > and apply the patch
> >     shown in the attachment.
> >
> > 4. Start code building:
> >    cd lustre-2.16.1
> >    ./configure --prefix=/opt/lustre
> > --with-linux=/usr/src/linux-headers-6.12.57+deb13-amd64
> > --disable-server --enable-mpitests=no
> >    make
> >    make install
> >
> > Now we can mount the Lustre file system with this command:
> >
> > mount -t lustre -o flock <mds_IP>@tcp:/chome /home
> >
> > where Lustre servers run Lustre-2.15.3. From the preliminary tests, it
> > seems OK. But we are not confident that our patch is OK. We still need
> > to test more extensively. So we hope that Lustre developer team could
> > help to review this patch.
> >
> > Best Regards,
> > T.H.Hsieh
> >
> > _______________________________________________
> > lustre-discuss mailing list
> > lustre-discuss at lists.lustre.org
> >
> https://urldefense.com/v3/__http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!NpxR!iW2pEy39hVgXxK7YXI8rXbizoLKD3CSOJqkMUEL48L7KPqLULWQH6US6GYF1yr9Qecxwm952JzfRteSYI4P__QuuJBmJi-9W$
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20251224/e1245410/attachment.htm>