From: Chuck Lever <chuck.lever@oracle.com>
To: "Yan, Haixiao (CN)" <haixiao.yan.cn@windriver.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Neil Brown <neil@brown.name>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfs mount failed with ipv6 addr
Date: Wed, 21 May 2025 11:03:28 -0400 [thread overview]
Message-ID: <9bc18e5e-86ba-4ac1-99f3-2335afd98fb4@oracle.com> (raw)
In-Reply-To: <6bb8f01e-628d-4353-8ed5-f77939e99df9@windriver.com>
On 5/21/25 10:11 AM, Yan, Haixiao (CN) wrote:
> On linux-5.10.y, my testcase run failed:
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount -
> t nfs [::1]:/mnt/nfs_root /mnt/v6 -o nfsvers=3
> mount.nfs: requested NFS version or transport protocol is not supported
>
> The first bad commit is:
>
> commit 7229200f68662660bb4d55f19247eaf3c79a4217
> Author: Chuck Lever <chuck.lever@oracle.com>
> Date: Mon Jun 3 10:35:02 2024 -0400
>
> nfsd: don't allow nfsd threads to be signalled.
>
> [ Upstream commit 3903902401451b1cd9d797a8c79769eb26ac7fe5 ]
commit 3903902401451b1cd9d797a8c79769eb26ac7fe5
Author: NeilBrown <neilb@suse.de>
AuthorDate: Tue Jul 18 16:38:08 2023 +1000
Commit: Chuck Lever <chuck.lever@oracle.com>
CommitDate: Tue Aug 29 17:45:22 2023 -0400
nfsd: don't allow nfsd threads to be signalled.
Adding Neil and the linux-nfs@ list ...
> Here is the test log:
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# dd if=/
> dev/zero of=/tmp/nfs.img bs=1M count=100
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB, 100 MiB) copied, 0.0386658 s, 2.7 GB/s
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkfs /
> tmp/nfs.img
> mke2fs 1.46.1 (9-Feb-2021)
> Discarding device blocks: 1024/102400\b\b\b\b\b\b\b\b\b\b\b\b\b
> \b\b\b\b\b\b\b\b\b\b\b\b\bdone
> Creating filesystem with 102400 1k blocks and 25688 inodes
> Filesystem UUID: 77e3bc56-46bb-4e5c-9619-d9a0c0999958
> Superblock backups stored on blocks:
> 8193, 24577, 40961, 57345, 73729
>
> Allocating group tables: 0/13\b\b\b\b\b \b\b\b\b\bdone
> Writing inode tables: 0/13\b\b\b\b\b \b\b\b\b\bdone
> Writing superblocks and filesystem accounting information:
> 0/13\b\b\b\b\b \b\b\b\b\bdone
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount /
> tmp/nfs.img /mnt
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkdir /
> mnt/nfs_root
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# touch /
> etc/exports
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# echo '/
> mnt/nfs_root *(insecure,rw,async,no_root_squash)' >> /etc/exports
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# /opt/
> wr-test/bin/svcwp.sh nfsserver restart
> stopping mountd: done
> stopping nfsd: ..........failed
> using signal 9:
> ..........failed
> exportfs: /etc/exports [1]: Neither 'subtree_check' or
> 'no_subtree_check' specified for export "*:/mnt/nfs_root".
> Assuming default behaviour ('no_subtree_check').
> NOTE: this default has changed since nfs-utils version 1.0.x
>
> starting 8 nfsd kernel threads: done
> starting mountd: done
> exportfs: /etc/exports [1]: Neither 'subtree_check' or
> 'no_subtree_check' specified for export "*:/mnt/nfs_root".
> Assuming default behaviour ('no_subtree_check').
> NOTE: this default has changed since nfs-utils version 1.0.x
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# echo
> hello > /mnt/nfs_root/hello.txt
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mkdir /
> mnt/v6
>
> root@intel-x86-64:/opt/wr-test/testcases/userspace/nfs-utils_v6# mount -
> t nfs [::1]:/mnt/nfs_root /mnt/v6 -o nfsvers=3
> mount.nfs: requested NFS version or transport protocol is not supported
>
> Thanks,
> Haixiao
>
I am not able to reproduce this behavior:
[root@pynfs-nfsd ~]# mount -v -o vers=3 [::1]:/export/pynfs-4.0 /mnt
mount.nfs: timeout set for Wed May 21 10:55:59 2025
mount.nfs: trying text-based options 'vers=3,addr=::1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying ::1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying ::1 prog 100005 vers 3 prot UDP port 20048
[root@pynfs-nfsd ~]# nfsstat -m
/mnt from [::1]:/export/pynfs-4.0
Flags:
rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,mountaddr=::1,mountvers=3,mountport=20048,mountproto=udp6,local_lock=none,addr=::1
[root@pynfs-nfsd ~]# uname -r
5.10.237-g024a4a45fdf8
[root@pynfs-nfsd ~]# cat /etc/redhat-release
Fedora release 33 (Thirty Three)
[root@pynfs-nfsd ~]#
Maybe I missed something.
--
Chuck Lever
parent reply other threads:[~2025-05-21 15:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6bb8f01e-628d-4353-8ed5-f77939e99df9@windriver.com>]
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=9bc18e5e-86ba-4ac1-99f3-2335afd98fb4@oracle.com \
--to=chuck.lever@oracle.com \
--cc=haixiao.yan.cn@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=stable@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