Re: NFS+GD issues on kernel 2.6.24, but not 2.6.22

[Trond Myklebust <trond.myklebust@fys.uio.no>]

On Thu, 2008-05-15 at 09:55 -0600, Adam Olsen wrote:
> On Thu, May 15, 2008 at 9:46 AM, Jeff Layton <jlayton@redhat.com> wrote:
> >  It really depends on the program, but I'd guess that it saw something
> >  in the fstat64() call that it didn't like. You might want to use strace
> >  with '-v -s 256' or something and look for differences in the info
> >  returned by the fstat64 call.
> 
> With the working kernel:
> 
> access("/mnt/isilon/fonts/arial.ttf", R_OK) = 0
> open("/mnt/isilon/fonts/arial.ttf", O_RDONLY) = 3
> fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
> fstat64(3, {st_dev=makedev(0, 25), st_ino=4634215,
> st_mode=S_IFREG|0666, st_nlink=1, st_uid=1001, st_gid=100,
> st_blksize=32768, st_blocks=194, st_size=48784,
> st_atime=2008/05/14-11:46:53, st_mtime=2008/05/14-11:46:53,
> st_ctime=2008/05/14-21:12:18}) = 0
> mmap2(NULL, 48784, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7a07000
> close(3)
> 
> With the *non* working kernel:
> 
> access("/mnt/isilon/fonts/arial.ttf", R_OK) = 0
> open("/mnt/isilon/fonts/arial.ttf", O_RDONLY) = 3
> fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
> fstat64(3, {st_dev=makedev(0, 23), st_ino=4299601510,
> st_mode=S_IFREG|0666, st_nlink=1, st_uid=1001, st_gid=100,
> st_blksize=32768, st_blocks=194, st_size=48784,
> st_atime=2008/05/14-11:46:53, st_mtime=2008/05/14-11:46:53,
> st_ctime=2008/05/14-21:12:18}) = 0
> close(3)                                = 0
> 
> Still looks almost identical, except the missing mmap2 in the
> non-working kernel.  Also, the st_ino is different... should they be
> the same?

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'.

  Trond