recent NFS problems?

[Jeff Garzik]

This is a bit weird.  Running 2.6.14-g6037d6bb (libata-dev.git branch 
'upstream') on both client and server.  Its latest Linux 
(7015faa7df829876a0f931cd18aa6d7c24a1b581) plus one libata patch.  All 
NFSv4 kernel options are enabled, on both client and server.

On Host A, I mirror a local directory /garz/nsmail to an NFS directory 
Host_B:/g/g/nsmail via rsync+ssh.  Host A also NFS mounts Host_B:/g 
locally.  mount on Host A says

	host_b:/g on /g type nfs (rw,tcp,intr,posix,addr=10.10.10.1)

Seeing some directory weirdness, where wildcard matches fail 
(NFS-related dcache bugs?) but direct accesses succeed:

[jgarzik@host_a~]$ ssh host_b "ls -d /g/g/nsmail/Trash.sbd/*11*"
/g/g/nsmail/Trash.sbd/Sent.20051105
/g/g/nsmail/Trash.sbd/Sent.20051105.msf
/g/g/nsmail/Trash.sbd/Sent.20051105.sbd
/g/g/nsmail/Trash.sbd/Trash.20051105
/g/g/nsmail/Trash.sbd/Trash.20051105.msf
/g/g/nsmail/Trash.sbd/Trash.20051105.sbd

[jgarzik@host_a ~]$ ls -d /g/g/nsmail/Trash.sbd/*11*
ls: /g/g/nsmail/Trash.sbd/*11*: No such file or directory

[jgarzik@host_a ~]$ ls -l /g/g/nsmail/Trash.sbd/Trash.20051105
-rw-rw-r--  1 jgarzik jgarzik 67484129 Nov  5 00:02 
/g/g/nsmail/Trash.sbd/Trash.20051105

[jgarzik@host_a~]$ wc -l /g/g/nsmail/Trash.sbd/Trash.20051105
1739088 /g/g/nsmail/Trash.sbd/Trash.20051105
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/