Once upon a time ceph-fuse did its own internal hash-map of live inodes to handle that (by just remembering which 64-bit inode any 32-bit one actually referred to). Unfortunately I believe this has been ripped out because it caused problems when the kernel tried to do lookups on 32-bit inodes that were so old they'd been recycled or dropped out of the mapping table. It's conceivable the kernel can implement this more safely and I'd certainly defer to Zheng or somebody as this is just out of my head and from prepping the source tree to see what still exists, but I would not expect it to be a safe long-term solution. -Greg On Tue, Oct 15, 2019 at 12:01 PM Janne Johansson <icepic.dz@xxxxxxxxx> wrote: > > > > Den tis 15 okt. 2019 kl 19:40 skrev Nathan Fish <lordcirth@xxxxxxxxx>: >> >> I'm not sure exactly what would happen on an inode collision, but I'm >> guessing Bad Things. If my math is correct, a 2^32 inode space will >> have roughly 1 collision per 2^16 entries. As that's only 65536, >> that's not safe at all. > > > Yeah, the birthday paradox will make sure you hit it very soon. 8-( > > -- > May the most significant bit of your life be positive. > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |