Date: Mon, 11 Mar 2002 23:09:48 +0100 From: Christoph Hellwig <hch@caldera.de> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Harti Brandt <brandt@fokus.gmd.de>, Garance A Drosihn <drosih@rpi.edu>, Poul-Henning Kamp <phk@critter.freebsd.dk>, arch@FreeBSD.ORG Subject: Re: Increasing the size of dev_t and ino_t Message-ID: <20020311230948.A2914@caldera.de> In-Reply-To: <Pine.NEB.3.96L.1020311160835.46602A-100000@fledge.watson.org>; from rwatson@FreeBSD.ORG on Mon, Mar 11, 2002 at 04:16:48PM -0500 References: <20020311172142.K1371-100000@beagle.fokus.gmd.de> <Pine.NEB.3.96L.1020311160835.46602A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.. Christoph -- Of course it doesn't work. We've performed a software upgrade. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020311230948.A2914>