On Tue, 2013-04-16 at 12:41 +0200, Joakim Tjernlund wrote: > Here we go again, this time i happened while browsing the Boston news on > www.dn.se > Now gvfsd-metadata is turned off(not running at all) and I get: > 10:28:44.616146 IP 192.168.201.44.nfs > 172.20.4.10.3671768838: reply ok > 52 getattr ERROR: unk 10024 Part of the reason why you are getting no response to these posts is that you are posting tcpdump-decoded data. Tcpdump still has no support for NFSv4, and therefore completely garbles the output by trying to interpret it as NFSv2/v3. In general, if you are posting network traffic, please record it as binary raw packet data (using the '-w' option on tcdump) so that we can look at the full contents. Either include it as an attachment, or provide us with details on how to download it from an http server. Other information that is needed in order to make sense of NFS bug reports includes: - client OS (non-linux) or kernel version (linux) - mount options on the client - server OS (non-linux) or kernel version (linux) - type of exported filesystem on the server - contents of /etc/exports on the server Please ensure that you always include those in your emails. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- 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
