id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
74	libc: inode id & copy	bird	bird	"The current inode number scheme is missing one bit in it's implementation. When we're copying files using OS/2 facilities, or even zipping/unzipping stuff, we end up creating duplicate inode numbers. 

The inode number generation is made up of two 32-bit numbers generated from the cannonized native path of the object. We then distiguish between creating a new object, correcting the inode value of an existing object, and generating a completely new one for an existing one. In the first case we have to generate both parts, and we use crc32 and sdbm for that. In the second case we read the inode number from the disk, but we regenerates the sdbm part. In the third case we generate both using djb2 and sdbm."	defect	assigned	normal		libc-backend	0.6	normal		inode number