Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 May 2024 23:39:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 279138] NFS and NFSUPG and BUFWAIT
Message-ID:  <bug-279138-227-H6X2tloLbs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-279138-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-279138-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279138

--- Comment #4 from Rick Macklem <rmacklem@FreeBSD.org> ---
(In reply to dgilbert from comment #2)
"fileid changed" normally occurs when multiple NFS
clients have the same /etc/hostid (due to cloning of
system images or ???). This will confuse the server,
since it will think the clients are the same client.

If you have multiple clients doing NFSv4 mounts, make
sure each one of them has a unique /etc/hostid.
(If your NFS mounts are NFSv3, I do not have an explanation
for "fileid changed". Long ago it was caused by a weird
broken NFS cache device, but I doubt any of those still exists.)

If your clients all have unique /etc/hostid's (and had them at
mount time), and you still see problems,
you could try reverting this commit:
fbe965591f8a
I don't see how it could cause a hang, but it is the only
recent change related to directory reading.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279138-227-H6X2tloLbs>