From nobody Sun Jul 03 09:57:33 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DFAF38A95B3 for ; Sun, 3 Jul 2022 09:58:11 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [85.220.129.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LbPWk5W5Yz4rSM for ; Sun, 3 Jul 2022 09:58:10 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 9DA4710A330B for ; Sun, 3 Jul 2022 11:58:03 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id B156810A3308 for ; Sun, 3 Jul 2022 11:58:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1656842281; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=nnfPPIgM56ydXTpLcH2k/OZ6xZHBJJ8mJt+NamzRW/o=; b=DHmB5nIQCYDLoN5jWakfBt1BjCG5FmMdSgp6w1NyPHz/IHH5L/+7k4rKLAGn6NAQHyAOi6 LQnp/Vlx0AhaEg0KFlbk2Op0TTFtwRdnZPrXF+X/1L9ICL6o88L2QOfVvyQ4IUPaVEIezy JSoN/7ahRL6223mzdJaRIh2eNyfhU+IzD21yXAgiv05D9cI13Va1G2NYzZujIlpf/6G4Gm 0GR5GGZwrvLl3KcFhNNb90VvoiNgSDYlwCM8DSKecoIfYIbv19vaIael4a/pJt67/IY2cO iJLn417CK+g4FrExuJPOWkeJqwOCO/RVCZC9fhNwatIG+r6zJneIfwHa600uGg== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-011-054-133.77.11.pool.telefonica.de [77.11.54.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 7C32F10A3306 for ; Sun, 3 Jul 2022 11:58:01 +0200 (CEST) Date: Sun, 3 Jul 2022 11:57:33 +0200 From: FreeBSD User To: FreeBSD CURRENT Subject: NFSv4: Invalid fstype: Invalid argument Message-ID: <20220703115800.5e150d95@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: e980c4 X-Rspamd-UID: 69b4f7 X-Rspamd-Queue-Id: 4LbPWk5W5Yz4rSM X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=DHmB5nIQ; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.31) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [0.14 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; RECEIVED_SPAMHAUS_PBL(0.00)[77.11.54.133:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt-de.de]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-0.90)[-0.896]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+]; NEURAL_SPAM_LONG(0.43)[0.433]; MLMMJ_DEST(0.00)[freebsd-current]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.31:from] X-ThisMailContainsUnwantedMimeParts: N Hello folks, Trying to mount a NFS filesystem offered by a FreeBSD 12.3-p5 (XigmaNAS) from a recent CURRENT (FreeBSD 14.0-CURRENT #19 main-n256512-ef86876b846: Sat Jul 2 23:31:53 CEST 2022 amd64) via :/etc # mount -t nfs -o vers=4 192.168.0.11:/mnt/NAS00/home /tmp/mnt results in mount_nfs: nmount: /tmp/mnt, Invalid fstype: Invalid argument and checking whether I can mount NFSv3 (I have explicitely set NFSv4 only on the server side, see below) via :/etc # mount -t nfs -o vers=3,mntudp 192.168.0.11:/mnt/NAS00/home /tmp/mnt [udp] 192.168.0.11:/mnt/NAS00/home: RPCPROG_NFS: RPC: Program not registered or :/etc # mount -t nfs -o vers=3,mntudp [fd01:a37::11]:/mnt/NAS00/home /tmp/mnt [udp6] fd01:a37::11:/mnt/NAS00/home: RPCPROG_NFS: RPC: Program not registered Womdering about the TCP conenction attempts, I checked the configurations on both, the CURRENT and XigmaNAS (server) side. [... server side ...] nas01: ~# ps -waux|grep mountd root 4332 0.0 0.0 11684 2652 - Is 23:13 0:00.01 /usr/sbin/mountd -l -r -S -R /etc/exports /etc/zfs/exports rpcinfo -p program vers proto port service 100000 4 tcp 111 rpcbind 100000 3 tcp 111 rpcbind 100000 2 tcp 111 rpcbind 100000 4 udp 111 rpcbind 100000 3 udp 111 rpcbind 100000 2 udp 111 rpcbind 100000 4 local 111 rpcbind 100000 3 local 111 rpcbind 100000 2 local 111 rpcbind 100024 1 udp 671 status 100024 1 tcp 671 status 100021 0 udp 1003 nlockmgr 100021 0 tcp 603 nlockmgr 100021 1 udp 1003 nlockmgr 100021 1 tcp 603 nlockmgr 100021 3 udp 1003 nlockmgr 100021 3 tcp 603 nlockmgr 100021 4 udp 1003 nlockmgr 100021 4 tcp 603 nlockmgr I do not see mountd nor nfsd being registered, hope this is all right within a NFSv4-only environment. Well, on the CURRENT server that provides without flaws NFSv4 for the CURRENT client I try to access the XigmaNAS NFSv4 fs from, rpcinfo looks like: (current server): root@walhall:/usr/src # rpcinfo -p program vers proto port service 100000 4 tcp 111 rpcbind 100000 3 tcp 111 rpcbind 100000 2 tcp 111 rpcbind 100000 4 udp 111 rpcbind 100000 3 udp 111 rpcbind 100000 2 udp 111 rpcbind 100000 4 local 111 rpcbind 100000 3 local 111 rpcbind 100000 2 local 111 rpcbind 100024 1 udp 774 status 100024 1 tcp 774 status 100021 0 udp 746 nlockmgr 100021 0 tcp 661 nlockmgr 100021 1 udp 746 nlockmgr 100021 1 tcp 661 nlockmgr 100021 3 udp 746 nlockmgr 100021 3 tcp 661 nlockmgr 100021 4 udp 746 nlockmgr 100021 4 tcp 661 nlockmgr Well, I also checked from client to current server and client to XigmaNAS server via rpcinfo -p and I get always the very same result. Checking the accessibility of the server host on the net via nmap gives this result (please be aware we use a dual stack network and need both IPv6 and IPv4 access so this attempt shows IPv4 access, but IPv6 access is also granted and assured): UDP: :/etc # nmap -sU 192.168.0.11 Starting Nmap 7.91 ( https://nmap.org ) at 2022-07-03 11:05 CEST Nmap scan report for nas01.intern (192.168.0.11) Host is up (0.00094s latency). Not shown: 996 closed ports PORT STATE SERVICE 111/udp open rpcbind 514/udp open|filtered syslog 2049/udp open nfs 5353/udp open zeroconf and TCP (since port 2049/NFSv4 is tcp): :/etc # nmap -sS 192.168.0.11 Starting Nmap 7.91 ( https://nmap.org ) at 2022-07-03 11:34 CEST Nmap scan report for nas01.intern (192.168.0.11) Host is up (0.00074s latency). Not shown: 996 closed ports PORT STATE SERVICE 22/tcp open ssh 111/tcp open rpcbind 443/tcp open https 2049/tcp open nfs I'm out of ideas here. What does mount_nfs: nmount: /tmp/mnt, Invalid fstype: Invalid argument mean? Is it the server reporting that it doesn't serve the requested fstyp or is there an issue with the local filesystem/mountpoint (located on UFS/FFS, the backend NFS fs are all located on ZFS)? I'm drifting like a dead man in the water here and I did not find aome answeres to the error reported here in the net applicable to the problem seen. Some hints are highly appreciated. Tahnks in advance and kind regards, oh -- O. Hartmann