Linux NFS development
 help / color / mirror / Atom feed
From: "Zhou Jifeng" <zhoujifeng@kylinsec.com.cn>
To: "Chuck Lever" <cel@kernel.org>, linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: Can the PNFS blocklayout of the Linux nfsd server be used in a production environment?
Date: Fri, 28 Nov 2025 16:12:14 +0800	[thread overview]
Message-ID: <tencent_013D77524EB6303F7D357E60@qq.com> (raw)
In-Reply-To: <5e1b3d07-fd80-47d0-bbf8-726d1f01ba54@app.fastmail.com>

>>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.
> 
> Pure block has some protocol deficiencies that prevent the ability
> of the MDS to fence pNFS clients, so it might never be production
> ready.
> 
> NFSD's pNFS block layout with iSCSI or SCSI works well in recent
> kernels, but has some quirks that still need to be addressed. You
> will have to test it with your favorite workloads to see whether
> it will work for you.
> 
> NFSD's pNFS block layout with NVMe implementation is fresh from the
> factory (I think the implementation went into v6.12?). As with
> iSCSI/SCSI, try it and see if it works well enough for you.
> 
> 
> --
> Chuck Lever

Hi Chuck,

I'm truly honored to receive your personal response, which has been 
extremely helpful to me. I've searched extensively online for methods 
to deploy pNFS clusters with nfsd, but most resources are incomplete. 
The documentation at 
"https://docs.kernel.org/admin-guide/nfs/pnfs-block-server.html" also 
provides very limited information. Are there any official, more 
comprehensive deployment guides for pNFS available.

Best regards,
ZhouJifeng

  reply	other threads:[~2025-11-28  8:12 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 [this message]
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
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=tencent_013D77524EB6303F7D357E60@qq.com \
    --to=zhoujifeng@kylinsec.com.cn \
    --cc=cel@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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