From: "matteo.debiaggi" <matteo.debiaggi@charta.it>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: Lock problem.
Date: Thu, 11 Oct 2007 15:07:30 +0200 [thread overview]
Message-ID: <470E2012.5020808@charta.it> (raw)
In-Reply-To: <18189.63030.815930.43180@notabene.brown>
Well, the result of tcpdump of the packets seen in the uncorrect lock
scenario
14:48:56.154531 CLIENT.3542368298 > SERVER.nfs: 108 getattr [|nfs] (DF)
14:48:56.154984 SERVER.nfs > CLIENT.3542368298: reply ok 112 getattr
[|nfs] (DF)
14:48:56.155158 CLIENT.3559145514 > SERVER.nfs: 112 access [|nfs] (DF)
14:48:56.155307 SERVER.nfs > CLIENT.3559145514: reply ok 120 access
[|nfs] (DF)
// FIRST LOCK
14:48:56.155423 CLIENT.1022 > SERVER.lockd: udp 180 (DF)
14:48:56.155713 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:48:56.163972 SERVER.823 > CLIENT.34865: udp 164 (DF)
14:48:56.164156 CLIENT > SERVER: icmp: CLIENT udp port 34865 unreachable
[tos 0xc0]
14:48:57.096559 arp who-has SERVER tell CLIENT
14:48:57.096618 arp reply SERVER is-at xxxxxxxxxxx
14:49:16.156340 SERVER.756 > CLIENT.sunrpc: udp 84 (DF)
14:49:16.156598 CLIENT.sunrpc > SERVER.756: udp 28 (DF)
14:49:16.156872 SERVER.823 > CLIENT.34865: udp 164 (DF)
14:49:16.157078 CLIENT > SERVER: icmp: CLIENT udp port 34865 unreachable
[tos 0xc0]
14:49:21.157083 arp who-has SERVER tell CLIENT
14:49:21.157136 arp reply SERVER is-at xxxxxxxxxx
14:49:26.157197 CLIENT.1022 > SERVER.lockd: udp 180 (DF)
14:49:26.157637 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:49:26.157830 CLIENT.3575922730 > SERVER.nfs: 112 access [|nfs] (DF)
14:49:26.158025 SERVER.nfs > CLIENT.3575922730: reply ok 120 access
[|nfs] (DF)
14:49:26.158157 CLIENT.3592699946 > SERVER.nfs: 108 getattr [|nfs] (DF)
14:49:26.158220 SERVER.nfs > CLIENT.3592699946: reply ok 112 getattr
[|nfs] (DF)
14:49:26.158402 CLIENT.3609477162 > SERVER.nfs: 112 access [|nfs] (DF)
14:49:26.158465 SERVER.nfs > CLIENT.3609477162: reply ok 120 access
[|nfs] (DF)
14:49:26.158653 CLIENT.3626254378 > SERVER.nfs: 124 lookup [|nfs] (DF)
14:49:26.158717 SERVER.nfs > CLIENT.3626254378: reply ok 240 lookup
[|nfs] (DF)
14:49:26.158904 CLIENT.3643031594 > SERVER.nfs: 124 lookup [|nfs] (DF)
14:49:26.158960 SERVER.nfs > CLIENT.3643031594: reply ok 240 lookup
[|nfs] (DF)
14:49:26.159156 CLIENT.3659808810 > SERVER.nfs: 124 remove [|nfs] (DF)
14:49:26.165118 SERVER.nfs > CLIENT.3659808810: reply ok 144 remove
[|nfs] (DF)
/////SECOND LOCK
14:49:26.165300 CLIENT.1022 > SERVER.lockd: udp 164 (DF)
14:49:26.165511 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:49:26.165661 CLIENT.1022 > SERVER.lockd: udp 180 (DF)
14:49:26.165867 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:49:26.167697 SERVER.905 > CLIENT.34667: udp 164 (DF)
14:49:26.167898 CLIENT > SERVER: icmp: CLIENT udp port 34667 unreachable
[tos 0xc0]
14:49:36.153446 SERVER.755 > CLIENT.sunrpc: udp 84 (DF)
14:49:36.153724 CLIENT.sunrpc > SERVER.755: udp 28 (DF)
14:49:46.162473 SERVER.754 > CLIENT.sunrpc: udp 84 (DF)
14:49:46.173694 CLIENT.sunrpc > SERVER.754: udp 28 (DF)
14:49:46.173900 SERVER.823 > CLIENT.34865: udp 164 (DF)
14:49:46.174070 CLIENT > SERVER: icmp: CLIENT udp port 34865 unreachable
[tos 0xc0]
14:49:51.173721 arp who-has SERVER tell CLIENT
14:49:51.173745 arp reply SERVER is-at 0:1:2:9c:74:c1
14:49:56.165858 CLIENT.34867 > SERVER.sunrpc: udp 88 (DF)
14:49:56.166362 SERVER.sunrpc > CLIENT.34867: udp 28 (DF)
14:49:56.166547 CLIENT.1022 > SERVER.lockd: udp 180 (DF)
14:49:56.166922 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:49:56.167068 CLIENT.3676586026 > SERVER.nfs: 108 getattr [|nfs] (DF)
14:49:56.167178 SERVER.nfs > CLIENT.3676586026: reply ok 112 getattr
[|nfs] (DF)
14:49:56.167288 CLIENT.3693363242 > SERVER.nfs: 120 read [|nfs] (DF)
14:49:56.167396 SERVER.nfs > CLIENT.3693363242: reply ok 1036 read
[|nfs] (DF)
14:49:56.167703 CLIENT.1022 > SERVER.lockd: udp 164 (DF)
14:49:56.167779 SERVER.lockd > CLIENT.1022: udp 36 (DF)
14:49:56.167949 CLIENT.3710140458 > SERVER.nfs: 112 access [|nfs] (DF)
14:49:56.168016 SERVER.nfs > CLIENT.3710140458: reply ok 120 access
[|nfs] (DF)
I've forgot to mention that some times i've got problem in the first
reader lock too(and it seems the same behaviour).
Do you need a tcpdump more detailed?(launched with wich options?)
Matteo.
P.S. : Yes, unlock followed by lock helps to avoid line reading
mismatches and havy load tests tell me it is reliable.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-11 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:56 Lock problem matteo.debiaggi
2007-10-11 10:08 ` Neil Brown
2007-10-11 13:07 ` matteo.debiaggi [this message]
2007-10-11 13:50 ` Talpey, Thomas
2007-10-11 14:24 ` matteo.debiaggi
2007-10-11 14:37 ` Talpey, Thomas
2007-10-11 15:23 ` matteo.debiaggi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470E2012.5020808@charta.it \
--to=matteo.debiaggi@charta.it \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.