On 2010-08-03, at 11:35, Dan Magenheimer wrote: > - The FS should be block-device-based (e.g. a ram-based FS > such as tmpfs should not enable cleancache) When you say "block device based", does this exclude network filesystems? It would seem cleancache, like fscache, is actually best suited to high-latency network filesystems. > - To ensure coherency/correctness, inode numbers must be unique > (e.g. no emulating 64-bit inode space on 32-bit inode numbers) Does it need to be restricted to inode numbers at all (i.e. can it use an opaque internal identifier like the NFS file handle)? Disallowing cleancache on a filesystem that uses 64-bit (or larger) inodes on a 32-bit system reduces its usefulness. Cheers, Andreas -- Andreas Dilger Lustre Technical Lead Oracle Corporation Canada Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html