>>>>> " " == Marcelo E Magallon <marcelo.magallon@bigfoot.com> writes:
> --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Hi,
> I just found some rather strange behaviour with an IRIX NFS
> server[1] and a Linux client (2.2.13 and 2.2.14). I have a
> directory (mail/Inbox/cur) where ls hangs like this:
> open("mail/Inbox/cur", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
> fstat(4, {st_mode=S_IFDIR|0755, st_size=23552, ...}) = 0
> fcntl(4, F_SETFD, FD_CLOEXEC) = 0 brk(0x805b000) = 0x805b000
> getdents(4, /* 78 entries */, 3391) = 3264 getdents(4, /* 1
> entries */, 3391) = 44 getdents(4, /* 1 entries */, 3391) = 44
> getdents(4, /* 1 entries */, 3391) = 44 [...]
> and remains like that until killed. The names of the files on
> the directory doesn't seem to matter as long as the lenghts of
> the filenames correspond to those found on the attached file.
> There are 312 files on the directory. If I just create a new
> file whose name lenght is between 1 and 9 characters, the
> problem dissapears. It doesn't work if I just use te first 78
> files. If I untar the attached tarball on a local ext2
> filesystem, there's no problem. The IRIX box doesn't have a
> problem either nor does a Sun box.
Does IRIX or Sun have a problem when using NFSv2? Also, it would be
helpful if you could provide the same strace as above, but using the
'-v' flag, so that we can see the cookie values returned by the
server.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:26 EST