Date: Wed, 20 Jul 2005 01:25:30 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: rwatson@FreeBSD.org Cc: src-committers@FreeBSD.org, pjd@FreeBSD.org, cvs-src@FreeBSD.org, alfred@FreeBSD.org, cvs-all@FreeBSD.org, ps@FreeBSD.org Subject: Re: cvs commit: src/sys/nfsclient nfs_socket.c Message-ID: <200507200825.j6K8PU1e042904@gw.catspoiler.org> In-Reply-To: <20050720091329.N50372@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Jul, Robert Watson wrote: > > On Tue, 19 Jul 2005, Alfred Perlstein wrote: > >>> I saw ESTALE errors on NFS clients after rebooting NFS server. >>> umount/mount was the only way to fix it. Your commit should fix my >>> problem? My machines are running 5-STABLE. >> >> Unlikely, the source of such a problem is probably that the order of >> mounted filesystems has changed and a different fsid was given to your >> exported fs. >> >> One way to fix it is to make sure that your fses are mounted in the >> right order each time. Or you can do a hack whereby exporting loads the >> fsid from a persistent file in the filesystem. > > I've been wondering for a while about the best way to address this, and a > possible start is to, on mount, attempt to derive the fsid from the uuid > of the file system (if present). We would need to then detect collisions > at run-time and fall back to an alternative fsid. The chances of a > collision are fairly low, so it might be an improvement over current > behavior. Why not specify the fsid as an option in /etc/exports?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507200825.j6K8PU1e042904>