Re: newnfs fileid changed "(BROKEN NFS SERVER OR MIDDLEWARE)"

From: Rick Macklem <rick.macklem_at_gmail.com>
Date: Wed, 27 Mar 2024 21:43:11 UTC 
On Wed, Mar 27, 2024 at 11:44 AM Bjoern A. Zeeb
<bzeeb-lists@lists.zabbadoz.net> wrote:
>
> Hi,
>
> I got this recently with both sides being FreeBSD when doing NFS root in
> the lab...
>
> newnfs: server '192.0.2.2' error: fileid changed. fsid 0:0: expected fileid 0x7034be6, got 0x7034a79. (BROKEN NFS SERVER OR MIDDLEWARE)
>
> Should I be worried?
It usually happens when you have more than one client with the same
/etchostid doing
NFSv4 mounts. Either make sure each client has a unique /etc/hostid or
do not use
NFSv4 mounts. The NFSv4 mounts will be broken, since the server thinks they are
the same client.

Often happens when systems are cloned. If you are using a diskless
root fs, I'm not
sure what you can do other than having a separate /etc/hostid for each of them.
(Maybe a symlink to a separate mounted fs?)

rick

>
> --
> Bjoern A. Zeeb                                                     r15:7
>