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 <d...@vanderster.com> 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 0x40008445FB3. > > I'm aware that CephFS is offsets the inode numbers by (mds_rank + 1) * > 2^40; in the case above the file is managed by mds.3. > > Did anyone see this same issue and find a workaround? (I read that > GlusterFS has an enable-in32 client option -- does CephFS have > something like that planned?) > > Thanks! > > Dan _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
