From: "Chuck Lever" <cel@kernel.org>
To: "Rick Macklem" <rick.macklem@gmail.com>
Cc: "Sebastian Feld" <sebastian.n.feld@gmail.com>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: LAYOUT4_NFSV4_1_FILES supported? Re: Can the PNFS blocklayout of the Linux nfsd server be used in a production environment?
Date: Mon, 01 Dec 2025 10:11:00 -0500 [thread overview]
Message-ID: <eee05a02-8f4a-4a41-8af1-c40900e4aed8@app.fastmail.com> (raw)
In-Reply-To: <CAM5tNy6jjeoN0H_JcD=8Ci4X8hU=4oyn3ZxRJrhpxJgApZUCcQ@mail.gmail.com>
On Fri, Nov 28, 2025, at 6:16 PM, Rick Macklem wrote:
> On Fri, Nov 28, 2025 at 8:24 AM Chuck Lever <cel@kernel.org> wrote:
>>
>>
>>
>> On Fri, Nov 28, 2025, at 3:57 AM, Sebastian Feld wrote:
>> > On Thu, Nov 27, 2025 at 5:41 PM Chuck Lever <cel@kernel.org> wrote:
>> >>
>> >> On Wed, Nov 26, 2025, at 9:14 PM, Zhou Jifeng wrote:
>> >> > Hello everyone, I learned through ChatGPT that the PNFS blocklayout of Linux
>> >> > nfsd cannot be used for production environment deployment. However, I saw
>> >> > a technical sharing conference video on YouTube titled "SNIA SDC 2024 - The
>> >> > Linux NFS Server in 2024" where it was mentioned that the PNFS blocklayout
>> >> > of nfsd has been fully maintained, which is contrary to the result given by
>> >> > ChatGPT.
>> >> >
>> >> > My question is: Can the PNFS blocklayout of nfsd be used for
>> >> > production environment deployment? If yes, from which kernel version can it
>> >> > be used in the production environment?
>> >>
>> >> Responding as the presenter of the SNIA SDC talk:
>> >>
>> >> There's a difference between "maintained" and "can be deployed in a
>> >> production environment". "Maintained" means there are developers
>> >> who are active and can help with bugs and new features. "Production
>> >> ready" means you can trust it with significant workloads.
>> >>
>> >> The pNFS block layout type has several subtypes. Pure block, iSCSI,
>> >> SCSI, and NVMe.
>> >
>> > What about the LAYOUT4_NFSV4_1_FILES layout type? Is that still supported?
>>
>> Above, we're talking about the Linux NFS server... IIRC NFSD never
>> supported the NFSv4.1 file layout type. It has a simple experimental
>> implementation of the flexfile layout type (the MDS and DS are the
>> same server).
> Once upon a time Benny Halevy had a single server (in the Linux
> kernel) that did file layout. (I remember because that is what I used
> for testing the FreeBSD client side.) It even knew how to do striping.
>
> However, it was a "single server" (MDS and DS in the same Linux kernel nfsd),
> so it was only useful for testing purposes.
>
> I have no idea if it is still around somewhere, but unless someone wants
> to do a lot of work on it, it is definitely not useful for production sites.
I am going to guess that was Dan Muntz's prototype. AFAIK that was
never merged upstream, but remains available in archive form at
git.linux-nfs.org.
NFSD continues to implement only the block-related layout types,
plus flexfile (in toy form).
--
Chuck Lever
next prev parent reply other threads:[~2025-12-01 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 2:14 Can the PNFS blocklayout of the Linux nfsd server be used in a production environment? Zhou Jifeng
2025-11-27 16:40 ` Chuck Lever
2025-11-28 8:12 ` Zhou Jifeng
2025-11-28 16:17 ` Chuck Lever
2025-11-28 8:57 ` LAYOUT4_NFSV4_1_FILES supported? " Sebastian Feld
2025-11-28 16:23 ` Chuck Lever
2025-11-28 23:16 ` Rick Macklem
2025-12-01 15:11 ` Chuck Lever [this message]
2025-12-02 6:09 ` Christoph Hellwig
2025-12-04 18:10 ` Dai Ngo
2025-12-05 8:05 ` Christoph Hellwig
2025-12-05 18:50 ` Dai Ngo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eee05a02-8f4a-4a41-8af1-c40900e4aed8@app.fastmail.com \
--to=cel@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rick.macklem@gmail.com \
--cc=sebastian.n.feld@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox