On 15/05/2008, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > Actually...my suspicion is that Trond is right and this app (or maybe a > library) doesn't like 64 bit inode numbers. It was probably not built > with LFS defines. glibc will turn that into a fstat64() system call, > and when it gets an inode number that won't fit in the field, it will > generate a -EOVERFLOW in userspace. You won't see it in an strace. An > ltrace *might* show it, or you could hook up gdb to your program and > try to look at it that way. We had a similar issue with Isilon NFS mounts - but only had an issue with non-LFS apps (32 bit) running on 64 bit clients - hence my previous question ... The 'fix' we use on the Isilon servers is to enable 32 bit 'fileids' on the server nodes - the fix is to add the line: vfs.nfsrv.do_32bit_fileid=1 to /etc/mcp/override/sysctl.conf (or create the file if it doesn't exist) on any node (it gets copied to all nodes and updated automagically) - however, _do not_ do this if you have any mounted clients as are likely to get stale mounts ... However, we get this issue with earlier 2.6 clients - so I'm not sure it is exactly the same problem ... James Pearson -- 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
