[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-18 Thread Darrell Enns
x27;t care about them anyway). See here for more details: https://www.tcm.phy.cam.ac.uk/sw/inodes64.html -Original Message- From: Yan, Zheng Sent: Wednesday, October 16, 2019 8:07 PM To: Dan van der Ster Cc: ceph-users Subject: [ceph-users] Re: CephFS and 32-bit Inode Numbers On M

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-16 Thread Yan, Zheng
On Mon, Oct 14, 2019 at 7:19 PM Dan van der Ster wrote: > > Hi all, > > One of our users has some 32-bit commercial software that they want to > use with CephFS, but it's not working because our inode numbers are > too large. E.g. his application gets a "file too big" error trying to > stat inode

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-16 Thread Dan van der Ster
t. > > Greetings > Ingo > > - Ursprüngliche Mail - > Von: "Nathan Fish" > An: "ceph-users" > Gesendet: Dienstag, 15. Oktober 2019 19:40:05 > Betreff: [ceph-users] Re: CephFS and 32-bit Inode Numbers > > I'm not sure exactly what would

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-16 Thread Ingo Schmidt
Data is correct. Greetings Ingo - Ursprüngliche Mail - Von: "Nathan Fish" An: "ceph-users" Gesendet: Dienstag, 15. Oktober 2019 19:40:05 Betreff: [ceph-users] Re: CephFS and 32-bit Inode Numbers I'm not sure exactly what would happen on an inode collision, but I'

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-15 Thread Gregory Farnum
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

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-15 Thread Janne Johansson
Den tis 15 okt. 2019 kl 19:40 skrev Nathan Fish : > 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

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-15 Thread Nathan Fish
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. On Mon, Oct 14, 2019 at 8:14 AM Dan van der Ster wrote: > > OK I found

[ceph-users] Re: CephFS and 32-bit Inode Numbers

2019-10-14 Thread Dan van der Ster
OK I found that the kernel has an "ino32" mount option which hashes 64 bit inos to 32-bit space. Has anyone tried this? What happens if two files collide? -- Dan On Mon, Oct 14, 2019 at 1:18 PM Dan van der Ster wrote: > > Hi all, > > One of our users has some 32-bit commercial software that they