From owner-freebsd-current@FreeBSD.ORG Wed Jan 14 12:14:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5368716A4CE; Wed, 14 Jan 2004 12:14:13 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB72843D5C; Wed, 14 Jan 2004 12:14:11 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i0EKCQUd051624; Wed, 14 Jan 2004 15:12:26 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i0EKCQNl051621; Wed, 14 Jan 2004 15:12:26 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 14 Jan 2004 15:12:26 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce Evans In-Reply-To: <20040115064753.T3550@gamplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Don Lewis cc: harti@freebsd.org cc: current@freebsd.org Subject: Re: simplifying linux_emul_convpath() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2004 20:14:13 -0000 On Thu, 15 Jan 2004, Bruce Evans wrote: > > That inode numbers are subject to collision is a practical reality with > > the existence of globally scalable distributed file systems. Many file > > formats, APIs, and ABIs assume a 32-bit inode number; however, distributed > > systems like AFS support hundreds of thousands, if not millions, of > > concurrent users and computer systems. Expecting each user/computer to > > It's a practical reality that file systems with inode numbers >= 2^32 > cannot work in FreeBSD now. So what ends up happening is what Coda and Arla do: take the 96-bit unique identifier (viceid or fid), hash it to a somewhat unique value, and stick the result in the vattr returned by VOP_GETATTR(). And sometimes applications just get confused. Of course, many of those applications were quite capable of getting confused before -- unless you hold a file open, you can't prevent its inode number from being reused if the file is deleted and a new one created. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research