On Thu, Oct 20, 2011 at 01:21:31PM -0400, Nikolaus Rath wrote: > I'm working on a FUSE file system that stores file system metadata in an > SQL database (http://code.google.com/p/s3ql/). Not having to keep track > of inode generation numbers would keep the code much simpler, because I > want to delete inode-rows from the SQL table when the last reference to > the inode is deleted (so I can't keep track of the generation no). You can use current time, or a counter, or something, as the generation number. > Now I'll either have to make inodes unique (and run into trouble after > 2^32 inodes have been used), or keep with the current scheme of > randomizing new inodes (which keeps the probability of problems low > enough but is ugly). With 2^32 inode numbers plus 2^32 generation numbers it should be possible to work something out that doesn't require remembering every old inode. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
