From owner-cvs-src@FreeBSD.ORG Wed Jul 20 08:55:06 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1F5616A41F; Wed, 20 Jul 2005 08:55:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61E4B43D45; Wed, 20 Jul 2005 08:55:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id DCEF846B0E; Wed, 20 Jul 2005 04:55:05 -0400 (EDT) Date: Wed, 20 Jul 2005 09:55:23 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Don Lewis In-Reply-To: <200507200825.j6K8PU1e042904@gw.catspoiler.org> Message-ID: <20050720095446.P50372@fledge.watson.org> References: <200507200825.j6K8PU1e042904@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2005 08:55:07 -0000 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