From: "Theodore Ts'o" <tytso@mit.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Cedric Blancher <cedric.blancher@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: LInux NFSv4.1 client and server- case insensitive filesystems supported?
Date: Sun, 8 Jun 2025 20:52:44 +0000 [thread overview]
Message-ID: <20250608205244.GD784455@mit.edu> (raw)
In-Reply-To: <643072ba-3ee6-4e5b-832a-aac88a06e51d@oracle.com>
On Sun, Jun 08, 2025 at 12:29:30PM -0400, Chuck Lever wrote:
>
> For some reason I thought case-insensitivity support was merged more
> recently than that. I recall it first appearing as a session at LSF in
> Park City, but maybe that one was in 2018.
commit b886ee3e778ec2ad43e276fd378ab492cf6819b7
Author: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Date: Thu Apr 25 14:12:08 2019 -0400
ext4: Support case-insensitive file name lookups
> nfs(5) describes the lookupcache= mount option. It controls how the
> Linux NFS client caches positive and negative lookup results.
Has anyone just tried it? It might just work. To create a
case-folded directory:
# mke2fs -Fq -t ext4 -O casefold /dev/vdc
# mount /dev/vdc /vdc
# mkdir /vdc/casefold
# chattr +F /vdc/casefold
# cp /etc/issue /vdc/casefold/MaDNeSS
# cat /vdc/casefold/madness
Then export the directory and mount it via NFS, and let us know how it
goes. I'm currently on a cruise ship so it's a bit harder for me to
do the experiment myself. :-)
- Ted
next prev parent reply other threads:[~2025-06-08 20:53 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 [this message]
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
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=20250608205244.GD784455@mit.edu \
--to=tytso@mit.edu \
--cc=cedric.blancher@gmail.com \
--cc=chuck.lever@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.