find returns wrong inode number?

[yunesj]

On my rofs-filterd fusefs, stat and ls give one inode number

# stat -c '%n %i' /mnt/backup-view/core
/mnt/backup-view/core 14852055

find gives a different inode number

# find /mnt/backup-view -maxdepth 1 -name core -printf '%p %i\n'
/mnt/backup-view/core 4294967295

Do you have any ideas as to what is going on?

Thanks!

[yunesj]

It looks related either to the FUSE use_ino option or the rofs-filtered callback_readdir implementation.