Re: FYI: amd64 system: "error: fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)"?

2021-11-18 Thread Mark Millard via freebsd-current
On 2021-Nov-18, at 15:54, Mark Millard  wrote:

> The ThreadRipper 1950X FreeBSD system is reporting a message at
> 03:01:10 or so for the last 3 days. The .148 is a aarch64 system
> (HoneyComb). None of the other systems (aarch64 Small Board
> Computers and a armv7 SBC) are reporting such.
> 
> Nov 16 03:01:10 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: 
> fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
> MIDDLEWARE)
> Nov 17 03:01:10 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: 
> fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
> MIDDLEWARE)
> Nov 18 03:01:09 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: 
> fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
> MIDDLEWARE)
> 
> # uname -apKU
> FreeBSD amd64_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #10 
> main-n250667-20aa359773be-dirty: Sun Nov 14 00:24:51 PST 2021 
> root@amd64_ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-NODBG
>   amd64 amd64 1400042 1400042
> 
> The .148 :
> 
> # uname -apKU
> FreeBSD HC_CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #19 
> main-n250667-20aa359773be-dirty: Sun Nov 14 02:57:32 PST 2021 
> root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
>   arm64 aarch64 1400042 1400042
> 
> (At times it is booted from a root-on-zfs media or a USB3 SSD UFS media
> instead but it is the same system build that is running for all those.)
> 


For reference:

I forgot to mention that the other aarch systems are running:

# uname -apKU
FreeBSD FBSDmacch 14.0-CURRENT FreeBSD 14.0-CURRENT #18 
main-n250455-890cae197737-dirty: Thu Nov  4 13:43:17 PDT 2021 
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
  arm64 aarch64 1400040 1400040

(all installed from the same build, so the example is sufficient).
The armv7 system is running:

# uname -apKU
FreeBSD OPiP2E_RPi2v11 14.0-CURRENT FreeBSD 14.0-CURRENT #14 
main-n250455-890cae197737-dirty: Thu Nov  4 16:13:56 PDT 2021 
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA7-nodbg-clang/usr/main-src/arm.armv7/sys/GENERIC-NODBG-CA7
  arm armv7 1400040 1400040

(At some point they will all be updated.)

This vintage difference might be part of why they do not
report anything.



===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




FYI: amd64 system: "error: fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)"?

2021-11-18 Thread Mark Millard via freebsd-current
The ThreadRipper 1950X FreeBSD system is reporting a message at
03:01:10 or so for the last 3 days. The .148 is a aarch64 system
(HoneyComb). None of the other systems (aarch64 Small Board
Computers and a armv7 SBC) are reporting such.

Nov 16 03:01:10 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: fileid 
changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
MIDDLEWARE)
Nov 17 03:01:10 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: fileid 
changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
MIDDLEWARE)
Nov 18 03:01:09 amd64_ZFS kernel: newnfs: server '192.168.1.148' error: fileid 
changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR 
MIDDLEWARE)

# uname -apKU
FreeBSD amd64_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #10 
main-n250667-20aa359773be-dirty: Sun Nov 14 00:24:51 PST 2021 
root@amd64_ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-NODBG
  amd64 amd64 1400042 1400042

The .148 :

# uname -apKU
FreeBSD HC_CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #19 
main-n250667-20aa359773be-dirty: Sun Nov 14 02:57:32 PST 2021 
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
  arm64 aarch64 1400042 1400042

(At times it is booted from a root-on-zfs media or a USB3 SSD UFS media
instead but it is the same system build that is running for all those.)


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)