From: Chuck Lever <chuck.lever@oracle.com>
To: Cedric Blancher <cedric.blancher@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4.x export options to mark export as case-insensitive, case-preserving? Re: LInux NFSv4.1 client and server- case insensitive filesystems supported?
Date: Tue, 9 Sep 2025 12:11:58 -0400 [thread overview]
Message-ID: <e1ca19a0-ab61-453f-9aea-ede6537ce9da@oracle.com> (raw)
In-Reply-To: <CALXu0UfgvZdrotUnyeS6F6qYSOspLg_xwVab8BBO6N3c9SFGfA@mail.gmail.com>
On 9/9/25 12:06 PM, Cedric Blancher wrote:
> Due lack of a VFS interface and the urgend use case of needing to
> export a case-insensitive filesystem via NFSv4.x, could we please get
> two /etc/exports options, one setting the case-insensitive boolean
> (true, false, get-default-from-fs) and one for case-preserving (true,
> false, get-default-from-fs)?
>
> So far LInux nfsd does the WRONG thing here, and exports even
> case-insensitive filesystems as case-sensitive. The Windows NFSv4.1
> server does it correctly.
Hi Cedric,
Can you send a pointer to some documentation for the Windows NFSv4.1
implementation of this feature?
--
Chuck Lever
next prev parent reply other threads:[~2025-09-09 16:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 17:58 LInux NFSv4.1 client and server- case insensitive filesystems supported? Cedric Blancher
2025-06-04 18:52 ` Cedric Blancher
2025-06-07 18:30 ` Chuck Lever
2025-06-07 22:39 ` Theodore Ts'o
2025-06-08 10:19 ` Jeff Layton
2025-06-08 16:29 ` Chuck Lever
2025-06-08 20:52 ` Theodore Ts'o
2025-06-08 21:52 ` Chuck Lever
2025-06-09 15:28 ` Gabriel Krisman Bertazi
2025-06-09 15:50 ` Theodore Ts'o
2025-06-09 16:41 ` Chuck Lever
2025-06-09 5:57 ` Christoph Hellwig
2025-06-09 14:16 ` Chuck Lever
2025-06-10 5:34 ` Christoph Hellwig
2025-09-09 16:06 ` NFSv4.x export options to mark export as case-insensitive, case-preserving? " Cedric Blancher
2025-09-09 16:11 ` Cedric Blancher
2025-09-09 16:11 ` Chuck Lever [this message]
2025-09-09 16:33 ` Cedric Blancher
2025-09-09 19:32 ` Chuck Lever
2025-09-10 10:44 ` Roland Mainz
2025-09-10 13:37 ` Rick Macklem
2025-09-11 8:07 ` fattr4_archive "deprecated" ? " Cedric Blancher
2025-09-11 15:01 ` Rick Macklem
2025-09-11 15:26 ` Trond Myklebust
2025-09-11 15:33 ` Cedric Blancher
2025-09-11 15:36 ` Cedric Blancher
2025-09-11 16:08 ` Cedric Blancher
2025-09-10 11:10 ` Jeff Layton
2025-09-10 14:14 ` Chuck Lever
2025-09-10 14:30 ` Jeff Layton
2025-09-10 14:35 ` Chuck Lever
2025-09-11 6:52 ` Cedric Blancher
2025-09-11 6:49 ` Cedric Blancher
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=e1ca19a0-ab61-453f-9aea-ede6537ce9da@oracle.com \
--to=chuck.lever@oracle.com \
--cc=cedric.blancher@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.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