Hello, Our FSAL does not support NFS4.1 yet and I'd like to refuse to mount for 4.1 version. I'm exploring 2 following options: 1/ A way to tell ganesha that we don't have export for 4.1 at init 2/ Return NOTSUPPORTED for one of the NFS message during mount stage (like PUTFH, GETATTR, etc). But related function in the fsal level do not have input param containing the minorversion. Can anyone give me a hint? Thank you
What makes your FSAL not support NFSv4.1? From the perspective of a FSAL, most of 4.1 has nothing special about it other than PNFS, support for which is explicitly enabled by the FSAL. Frank From: Tuan Viet Nguyen [mailto:ntvietvn@gmail.com] Sent: Tuesday, November 23, 2021 3:21 AM To: devel@lists.nfs-ganesha.org Subject: [NFS-Ganesha-Devel] Prohibit NFS4.1 mount Hello, Our FSAL does not support NFS4.1 yet and I'd like to refuse to mount for 4.1 version. I'm exploring 2 following options: 1/ A way to tell ganesha that we don't have export for 4.1 at init 2/ Return NOTSUPPORTED for one of the NFS message during mount stage (like PUTFH, GETATTR, etc). But related function in the fsal level do not have input param containing the minorversion. Can anyone give me a hint? Thank you
Good to know. It is just because we have never tested our FSAL with 4.1 and our usual test suites pass partially so while waiting for the whole investigation, we'd like to prohibit 4.1 mount to avoid surprises. Is there any way to do that? Thanks On Tue, Nov 23, 2021 at 3:40 PM Frank Filz <ffilzlnx@mindspring.com> wrote:
What makes your FSAL not support NFSv4.1? From the perspective of a FSAL, most of 4.1 has nothing special about it other than PNFS, support for which is explicitly enabled by the FSAL.
Frank
*From:* Tuan Viet Nguyen [mailto:ntvietvn@gmail.com] *Sent:* Tuesday, November 23, 2021 3:21 AM *To:* devel@lists.nfs-ganesha.org *Subject:* [NFS-Ganesha-Devel] Prohibit NFS4.1 mount
Hello,
Our FSAL does not support NFS4.1 yet and I'd like to refuse to mount for 4.1 version. I'm exploring 2 following options:
1/ A way to tell ganesha that we don't have export for 4.1 at init
2/ Return NOTSUPPORTED for one of the NFS message during mount stage (like PUTFH, GETATTR, etc). But related function in the fsal level do not have input param containing the minorversion.
Can anyone give me a hint?
Thank you
OK, there is a config for that… NSFV4 { Minor_Versions = 0; } It takes a list of allowed minor versions. Frank From: Tuan Viet Nguyen [mailto:ntvietvn@gmail.com] Sent: Tuesday, November 23, 2021 10:22 AM To: Frank Filz <ffilzlnx@mindspring.com> Cc: devel@lists.nfs-ganesha.org Subject: [NFS-Ganesha-Devel] Re: Prohibit NFS4.1 mount Good to know. It is just because we have never tested our FSAL with 4.1 and our usual test suites pass partially so while waiting for the whole investigation, we'd like to prohibit 4.1 mount to avoid surprises. Is there any way to do that? Thanks On Tue, Nov 23, 2021 at 3:40 PM Frank Filz <ffilzlnx@mindspring.com <mailto:ffilzlnx@mindspring.com> > wrote: What makes your FSAL not support NFSv4.1? From the perspective of a FSAL, most of 4.1 has nothing special about it other than PNFS, support for which is explicitly enabled by the FSAL. Frank From: Tuan Viet Nguyen [mailto:ntvietvn@gmail.com <mailto:ntvietvn@gmail.com> ] Sent: Tuesday, November 23, 2021 3:21 AM To: devel@lists.nfs-ganesha.org <mailto:devel@lists.nfs-ganesha.org> Subject: [NFS-Ganesha-Devel] Prohibit NFS4.1 mount Hello, Our FSAL does not support NFS4.1 yet and I'd like to refuse to mount for 4.1 version. I'm exploring 2 following options: 1/ A way to tell ganesha that we don't have export for 4.1 at init 2/ Return NOTSUPPORTED for one of the NFS message during mount stage (like PUTFH, GETATTR, etc). But related function in the fsal level do not have input param containing the minorversion. Can anyone give me a hint? Thank you
Thanks Frank ! On Tue, Nov 23, 2021 at 9:28 PM Frank Filz <ffilzlnx@mindspring.com> wrote:
OK, there is a config for that…
NSFV4 {
Minor_Versions = 0;
}
It takes a list of allowed minor versions.
Frank
*From:* Tuan Viet Nguyen [mailto:ntvietvn@gmail.com] *Sent:* Tuesday, November 23, 2021 10:22 AM *To:* Frank Filz <ffilzlnx@mindspring.com> *Cc:* devel@lists.nfs-ganesha.org *Subject:* [NFS-Ganesha-Devel] Re: Prohibit NFS4.1 mount
Good to know. It is just because we have never tested our FSAL with 4.1 and our usual test suites pass partially so while waiting for the whole investigation, we'd like to prohibit 4.1 mount to avoid surprises.
Is there any way to do that?
Thanks
On Tue, Nov 23, 2021 at 3:40 PM Frank Filz <ffilzlnx@mindspring.com> wrote:
What makes your FSAL not support NFSv4.1? From the perspective of a FSAL, most of 4.1 has nothing special about it other than PNFS, support for which is explicitly enabled by the FSAL.
Frank
*From:* Tuan Viet Nguyen [mailto:ntvietvn@gmail.com] *Sent:* Tuesday, November 23, 2021 3:21 AM *To:* devel@lists.nfs-ganesha.org *Subject:* [NFS-Ganesha-Devel] Prohibit NFS4.1 mount
Hello,
Our FSAL does not support NFS4.1 yet and I'd like to refuse to mount for 4.1 version. I'm exploring 2 following options:
1/ A way to tell ganesha that we don't have export for 4.1 at init
2/ Return NOTSUPPORTED for one of the NFS message during mount stage (like PUTFH, GETATTR, etc). But related function in the fsal level do not have input param containing the minorversion.
Can anyone give me a hint?
Thank you
participants (2)
-
Frank Filz -
Tuan Viet Nguyen