Re: nfs4 mount hanging suddenly

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

 



On Wed, 2012-02-29 at 16:21 -0700, Orion Poplawski wrote:
> On 02/29/2012 04:17 PM, J. Bruce Fields wrote:
> > On Wed, Feb 29, 2012 at 03:29:36PM -0700, Orion Poplawski wrote:
> >> Just starting today, one of our user's nfs mounted home directory
> >> has started locking up.  Client is Fedora 16 32-bit, server is
> >> CentOS 5.7 32-bit.  Have not seen this particular problem elsewhere
> >> (yet).
> >>
> >> I captured this trace on the server after the hang:
> >>
> >> http://sw.cora.nwra.com/tmp/marie-nfs-home-lwang-hang.pcap
> >>
> >>    1   0.000000  10.10.20.15 ->  10.10.10.1   NFS V4 COMP Call<EMPTY>
> >> PUTFH;GETATTR GETATTR
> >>    2   0.000133   10.10.10.1 ->  10.10.20.15  NFS V4 COMP Reply (Call
> >> In 1)<EMPTY>  PUTFH;GETATTR GETATTR
> >>    3   0.000421  10.10.20.15 ->  10.10.10.1   TCP 879>  nfs [ACK]
> >> Seq=137 Ack=225 Win=17738 Len=0 TSV=3584653 TSER=2438333196
> >>    4   0.000519  10.10.20.15 ->  10.10.10.1   NFS V4 COMP Call<EMPTY>
> >> PUTFH;ACCESS ACCESS;GETATTR GETATTR
> >>    5   0.000587   10.10.10.1 ->  10.10.20.15  NFS V4 COMP Reply (Call
> >> In 4)<EMPTY>  PUTFH;ACCESS ACCESS;GETATTR GETATTR[Unreassembled
> >> Packet [incorrect TCP checksum]]
> >>    6   0.040522  10.10.20.15 ->  10.10.10.1   TCP 879>  nfs [ACK]
> >> Seq=289 Ack=465 Win=17738 Len=0 TSV=3584694 TSER=2438333196
> >>    7   0.451636  10.10.20.15 ->  10.10.10.1   NFS V4 COMP Call<EMPTY>
> >> PUTFH;SAVEFH SAVEFH;OPEN OPEN;DELEGRETURN DELEGRETURN;Unknown
> >
> > That looks weird.  Looking at the pcap--ok, the "delegreturn" is a
> > mistake, there's no delegreturn there.
> >
> >>    8   0.451892   10.10.10.1 ->  10.10.20.15  NFS V4 COMP Reply (Call
> >> In 7)<EMPTY>  PUTFH;SAVEFH SAVEFH;OPEN OPEN(10008)
> >
> > That probably means the server is waiting for the client to return a
> > delegation.
> >
> > Either the server's confused about their being a delegation, or the
> > client's failing to return one it should?
> >

As far as I can see from your trace, the client keeps trying to open the
file '.history', and the server keeps replying with NFS4ERR_DELAY. There
is nothing in the trace itself that can tell us why the server is
delaying.

Cheers
  Trond

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com

��.n��������+%������w��{.n�����{��w���jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[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