On Thu, 15 May 2008 16:49:13 -0400 Jeff Layton <jlayton@xxxxxxxxxx> wrote: > On Thu, 15 May 2008 14:15:51 -0600 > "Adam Olsen" <arolsen@xxxxxxxxx> wrote: > > > On Thu, May 15, 2008 at 12:37 PM, Trond Myklebust > > <trond.myklebust@xxxxxxxxxx> wrote: > > > Looks as if you've got a 32-bit application that doesn't like 64-bit > > > inode numbers. Try booting with the kernel parameter > > > 'nfs.enable_ino64=0'. > > > > Ok, tried that. It's still a no go. > > > > I suggest some debugging of the actual application. Everything looks > fine from a system call standpoint. You'll need to debug the > application and figure out why it's not doing what you expect. > 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. Good luck -- Jeff Layton <jlayton@xxxxxxxxxx> -- 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
