Date: Wed, 20 Jul 2005 09:55:23 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Don Lewis <truckman@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: <20050720095446.P50372@fledge.watson.org> In-Reply-To: <200507200825.j6K8PU1e042904@gw.catspoiler.org> References: <200507200825.j6K8PU1e042904@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Jul 2005, Don Lewis wrote: >>> 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? The perils of manual configuration? Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050720095446.P50372>