Date: Thu, 18 Nov 2021 16:04:00 -0800 From: Mark Millard via freebsd-current <freebsd-current@freebsd.org> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: FYI: amd64 system: "error: fileid changed. fsid 0:0: expected fileid 0xa, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)"? Message-ID: <BCDAD1B2-199C-4CA5-9D12-7C53096312D5@yahoo.com> In-Reply-To: <E3D30111-F8BE-40E6-B606-431428E40F59@yahoo.com> References: <E3D30111-F8BE-40E6-B606-431428E40F59@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Nov-18, at 15:54, Mark Millard <marklmi@yahoo.com> 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. >=20 > 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) >=20 > # 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.a= md64/sys/GENERIC-NODBG amd64 amd64 1400042 1400042 >=20 > The .148 : >=20 > # 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/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400042 1400042 >=20 > (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.) >=20 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/arm6= 4.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.a= rmv7/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. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCDAD1B2-199C-4CA5-9D12-7C53096312D5>