From: Allen P. <pul...@co...> - 2007-08-27 21:06:57
|
I'm developing a FUSE interface to a multi-terabyte storage system. I'm looking for advice on how to handle ino's. I could give each file a permanent 32-bit ino. That would play nicely = with FUSE and 32-bit Linux, however, it would limit storage to 4 billion = files and require fairly expensive tracking and recycling of ino's. I could alternately give each file a permanent 64-bit ino. These would essentially be unlimited and they would not have to be tracked for recycling. If I went with 64-bit ino's, how would that play with FUSE and 32-bit = Linux? I understand FUSE can generate temporary 32-bit ino's which are valid = until the file system is unmounted. Is that correct? If I allow FUSE to = generate temporary ino's, how expensive is that (computation and memory usage) = and what functionality and compatibility problems will I run into under = standard 32-bit Linux and its user tools? Alternately, is there a way to recompile FUSE under 32-bit Linux to use = a file system's 64 bit ino's? Thank you, Allen |