From owner-freebsd-arch Mon Mar 11 14:15:54 2002 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EF9C337B402 for ; Mon, 11 Mar 2002 14:15:49 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2BMFXi48782; Mon, 11 Mar 2002 17:15:33 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 11 Mar 2002 17:15:32 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Christoph Hellwig Cc: Harti Brandt , Garance A Drosihn , Poul-Henning Kamp , arch@FreeBSD.ORG Subject: Re: Increasing the size of dev_t and ino_t In-Reply-To: <20020311230948.A2914@caldera.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 11 Mar 2002, Christoph Hellwig wrote: > On Mon, Mar 11, 2002 at 04:16:48PM -0500, Robert Watson wrote: > > The complicating factor comes when you try and map the 96-bit (plus realm) > > into the 32-bit inode number. FreeBSD runs fine, but some applications > > assuming the POSIX device number/inode number equality behave poorly. For > > example, gnu tar may find collisions and assume files are a hard link when > > they are not. Linux, on the other hand, uses the inode numbers within the > > kernel, and may panic if there is a collision. > > The only place Linux uses the inode number is the generic inode cache > implementation, which may or may not be used by filesystems. Also there > won't be panic because you can't read in two inodes having the same > i_ino when using it.. I may be dated: when we were working on the Coda port to Linux, once in a while the system would blow a fuse when there was an inode number collision. I remember some similar reports on Arla. However, that may have been 2.1.x or before, or/and I may have misunderstood the failure mode. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message