<div dir="ltr">Sorry, I should reply this message to the lustre-disscuss mailing list. So here I forwarded my reply.<div><br></div><div>Best Regards,</div><div>T.H.Hsieh<br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>\u5bc4\u4ef6\u8005\uff1a <strong class="gmail_sendername" dir="auto">Tung-Han Hsieh</strong> <span dir="auto"><<a href="mailto:tunghan.hsieh@gmail.com">tunghan.hsieh@gmail.com</a>></span><br>Date: 2025\u5e7412\u670824\u65e5\u9031\u4e09 \u4e0a\u534812:48<br>Subject: Re: [lustre-discuss] Patch of Lustre-2.16.1 to Linux kernel 6.12.57<br>To: Shaun Tancheff <<a href="mailto:shaun.tancheff@hpe.com">shaun.tancheff@hpe.com</a>><br></div><br><br><div dir="ltr">Dear Tancheff,<div><br></div><div>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:</div><div><br></div><div>(in root account)</div><div>(<mds> and <oss> installed Lustre-2.15.3)</div><div># mount -t lustre -o flock <mds>@tcp:/chome /mnt</div><div># cd /mnt</div><div># mkdir tmpdir</div><div># ls</div><div>ls: cannot open directory '.': No such file or directory</div><div><br></div><div>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).</div><div><br></div><div>For my patched Lustre-2.16.1, it also has this problem.</div><div><br></div><div>Currently it is not clear how to fix it. Probably Lustre-2.15.3 installed in the Lustre servers should be upgraded ?</div><div><br></div><div>Best Regards,</div><div>T.H.Hsieh</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Shaun Tancheff via lustre-discuss <<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a>> \u65bc 2025\u5e7412\u670822\u65e5\u9031\u4e00 \u4e0a\u53489:05\u5beb\u9053\uff1a<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/20/25 11:08, Tung-Han Hsieh via lustre-discuss wrote:<br>
> Greetings,<br>
><br>
> Recently we were requested to install Lustre client to a new machine, <br>
> installed Debian-13.2 (trixie), with Linux kernel 6.12.57. We install <br>
> it from compiling the source code. During installation, we encountered <br>
> a lot of compiling errors, due to changes of kernel API from version <br>
> 5.X.X to 6.12.X. We struggled quite a lot to update the code of <br>
> Lustre, and finally came out a patch, as shown in the attachment. I <br>
> would like to submit this patch to the Lustre developer team for <br>
> review and test, and finally being committed to the future versions of <br>
> Lustre. This is very important, because as newer machines shipped, we <br>
> are forced to install newer versions of Linux OS, and Linux kernel. We <br>
> hope that Lustre file system could work well in these new environments.<br>
><br>
The patch does not look too problematic, however you should be aware <br>
that Lustre 2.17-rc2 is currently building fine with 6.15, not sure what <br>
the state of back ports of kernel support are for Lustre 2.16.<br>
<br>
FWIW kernel support for 6.16 and 6.17 are enqueue and 6.18 is <br>
essentially done awaiting the new fs mount API changes James has done (I <br>
have not yet had a chance to test them together since I am traveling).<br>
<br>
> The steps of compiling Lustre in our new machine is following:<br>
><br>
> 1. Use "apt install" to install necessary code building packages, such <br>
> as build-essential, gcc,<br>
> make, autoconf, <br>
> libyaml-dev, uuid-dev, libblkid-dev, libnl-3-dev, libudev-dev, libkeyutils-dev, <br>
><br>
> libmount-dev, python3-dev, libnl-genl-3-dev, libtool, ...., etc.<br>
><br>
> 2. Install the kernel source, which is the version of the current <br>
> running kernel:<br>
> apt install linux-headers-6.12.57+deb13-amd64<br>
><br>
> 3. Download Lustre source 2.16.1 (the newest version we have found), <br>
> and apply the patch<br>
> shown in the attachment.<br>
><br>
> 4. Start code building:<br>
> cd lustre-2.16.1<br>
> ./configure --prefix=/opt/lustre <br>
> --with-linux=/usr/src/linux-headers-6.12.57+deb13-amd64 <br>
> --disable-server --enable-mpitests=no<br>
> make<br>
> make install<br>
><br>
> Now we can mount the Lustre file system with this command:<br>
><br>
> mount -t lustre -o flock <mds_IP>@tcp:/chome /home<br>
><br>
> where Lustre servers run Lustre-2.15.3. From the preliminary tests, it <br>
> seems OK. But we are not confident that our patch is OK. We still need <br>
> to test more extensively. So we hope that Lustre developer team could <br>
> help to review this patch.<br>
><br>
> Best Regards,<br>
> T.H.Hsieh<br>
><br>
> _______________________________________________<br>
> lustre-discuss mailing list<br>
> <a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a><br>
> <a href="https://urldefense.com/v3/__http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!NpxR!iW2pEy39hVgXxK7YXI8rXbizoLKD3CSOJqkMUEL48L7KPqLULWQH6US6GYF1yr9Qecxwm952JzfRteSYI4P__QuuJBmJi-9W$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!NpxR!iW2pEy39hVgXxK7YXI8rXbizoLKD3CSOJqkMUEL48L7KPqLULWQH6US6GYF1yr9Qecxwm952JzfRteSYI4P__QuuJBmJi-9W$</a><br>
<br>
<br>
_______________________________________________<br>
lustre-discuss mailing list<br>
<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org" rel="noreferrer" target="_blank">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br>
</blockquote></div>
</div></div></div>