Boaz Harrosh <bharrosh@xxxxxxxxxxx> wrote: >On 10/21/2011 10:44 AM, Nikolaus Rath wrote: >> Yes, with 64bit inodes everything would be fine. But fuse uses 'long' >> for inodes, so on 32bit systems you only have 32bit inodes even if >ino_t >> is 64bit. > >With out knowing any of the details, what kind of brain dead thing is >putting "long" in an API. What do you do with 32bit user-mode on 64bit >Kernel. It's called a bug, they are known to appear occasionally in computer software. > >32 bits for inode numbers is a broken system for 15 years already. >Fix the broken FUSE that falsely calls itself File-System and >stop bitching about NFS. It's FUSE you should be hacking and fixing. I merely answered the question of why I was interested in generation numbers in NFS4. Best, Nikolaus -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
