Re: NFS loop on 3.4.39

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> wrote on 2013/04/16 
17:36:55:

> From: "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx>
> To: Joakim Tjernlund <joakim.tjernlund@xxxxxxxxxxxx>, 
> Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx>
> Date: 2013/04/16 17:37
> Subject: Re: NFS loop on 3.4.39
> 
> 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:

Thank you Trond, I figured there was something missing but I didn't know 
where to start but here goes:

> 
> - client OS (non-linux) or kernel version (linux)
Client OS Linux 3.4.39, x86

> - mount options on the client
~ # ypmatch jocke auto.home
-fstype=nfs,soft devsrv:/mnt/home/jocke

> - server OS (non-linux) or kernel version (linux)
Server OS Linux 3.4.39, amd64

> - type of exported filesystem on the server
XFS

> - contents of /etc/exports on the server
more /etc/exports
# /etc/exports: NFS file systems being exported.  See exports(5).
/mnt/home              *(rw,async,root_squash,no_subtree_check)
/mnt/systemtest        *(rw,sync,root_squash,no_subtree_check)
/mnt/TNM               *(rw,sync,root_squash,no_subtree_check)
/tftproot              *(rw,async,root_squash,no_subtree_check)
/mnt/images *(rw,async,no_root_squash,no_subtree_check,insecure)
/rescue *(ro,async,no_root_squash,no_subtree_check,insecure)

/mnt/home is the one failing

> 
> Please ensure that you always include those in your emails.

nfs.pcap: 
http://ftp-us.transmode.se/get/?id=1bf2561ed2e7d4e379b2936319c82c25

nfs2.pcap: 
http://ftp-us.transmode.se/get/?id=759c7645248a426720da8e9ba7074040

nfs3.pcap: 
http://ftp-us.transmode.se/get/?id=051c6d771978b2407e15e96152bd6e66

nfs4.pcap: 
http://ftp-us.transmode.se/get/?id=5dfab4da6cbbe400697bc1621b541c9f

nfs3.pcap is the gvsd-metadata problem one can find using google, doesn't 
have to be a NFS problem
The other 3 all come from surfing the www using firefox 17.0.3
--
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




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux