Date: Tue, 13 Jan 2026 15:17:22 -0800 From: Mark Millard <marklmi@yahoo.com> To: Cedric Blancher <cedric.blancher@gmail.com>, freebsd-hackers@freebsd.org Cc: Rick Macklem <rick.macklem@gmail.com> Subject: Re: FreeBSD NFSv4.1 client and server - case insensitive filesystems supported? Message-ID: <748e57b4-1fca-4df3-b70f-605eedd4bb8b@yahoo.com> In-Reply-To: <CALXu0UfGggpQ9rbyX8kiRWt23gfTguk28oKKCdtXLP7z2W5yqA@mail.gmail.com> References: <CALXu0UfjR5ZuX1i1=_oUuhiF2%2B7G7d9qPydfwGqBM=Kgh90Jxg@mail.gmail.com> <CAM5tNy6-VcUjZuGDs%2BDBY-6_gNpbyiR5JkJOnUtU-vfN%2BTojug@mail.gmail.com> <CAM5tNy4tBMJH6j3tpOS-T2tGV9d3FMh1dwrLeBDD0urC3C-bZA@mail.gmail.com> <CALXu0Ucr4xfBJ%2BAd7THWHq2LObbHVTwKODi90vETXjciH-gWKw@mail.gmail.com> <785b4793-29e7-419e-9713-57c2f99b1d17@yahoo.com> <CALXu0UfGggpQ9rbyX8kiRWt23gfTguk28oKKCdtXLP7z2W5yqA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 1/13/26 14:48, Cedric Blancher wrote: > On Tue, 13 Jan 2026 at 22:41, Mark Millard <marklmi@yahoo.com> wrote: >> >> On 1/13/26 12:28, Cedric Blancher wrote: >>> On Mon, 12 Jan 2026 at 23:04, Rick Macklem <rick.macklem@gmail.com> wrote: >>>> >>>> On Mon, Jan 12, 2026 at 1:56 PM Rick Macklem <rick.macklem@gmail.com> wrote: >>>>> >>>>> On Mon, Jan 12, 2026 at 11:52 AM Cedric Blancher >>>>> <cedric.blancher@gmail.com> wrote: >>>>>> >>>>>> Good evening! >>>>>> >>>>>> Does the FreeBSD >= 14.3 NFSv4.1 client and server support case >>>>>> insensitive filesystems, e.g. exported ZFS or FAT? >>>>> Greater than, as in 15.0. >>>> Oops, that's 15.1-> >>>> (I looked and it is in stable/15, but not releng/15.0.) >>>> (I work with main and the stable branches and don't keep track of when the >>>> releases branch off.) >>> >>> OK, version confusion. :) >>> >>> What do I have to do as FreeBSD root user to update a FreeBSD 15.0 >>> installation to a kernel version which supports case-insensitive >>> filesystems for NFSv4.2 server, i.e. FATTR4_CASE_INSENSITIVE and >>> FATTR4_CASE_PRESERVING are set according to the features of ZFS? >>> >>> Ced >>> >>> >> >> >> As I understand what Rick wrote: >> >> ) No *.*-RELEASE supports such. (No releng/*.* branch has such code.) >> >> ) Modern 15.0-STABLE supports such (stable/15 branch has such code). >> >> ) Modern 16.0-CURRENT supports such (main branch has such code). >> >> Are you in a situation that allows use of the likes of some commit of, >> say, 15.0-STABLE ( branch stable/15 )? >> >> If you must have a *.*-RELEASE instead, you have to wait for >> 15.1-RELEASE to be available. > > OK, I have to do some outings: I am new to FreeBSD, and worse: I am > management (sort of rond-de-cuir). > > What do I have to do as user root in a FreeBSD 15.0 installation to > update to 15.0-STABLE to get working FATTR4_CASE_INSENSITIVE and > FATTR4_CASE_PRESERVING support in FreeBSD NFS server? My context has only ever had very simple configurations. But I do know that how to upgrade depends on which technique was used to install 15.0-RELEASE : If you have a installation based on the new pkgbase style of installation it would be different than if you had a installation via a historical technique. For the historical techniques (source code style installation vs. other historical styles of installation, for example), there is variability as well. You likely need to report various supporting information details describing the specific context that you would be starting from. Overall, I'm not likely to be an appropriate guide for any sort of production environment doing a FreeBSD OS upgrade, even with such information. > > Also, which FreeBSD commit added support for working > FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING? It is probably best if Rick answers the question about his own code. I've no knowledge of its details. That need not mean that he would be an proper source overall for how to upgrade the FreeBSD OS from 15.0-RELEASE to a vintage of 15.0-STABLE . -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?748e57b4-1fca-4df3-b70f-605eedd4bb8b>