From: Neil Brown <neilb@suse.de>
To: "Laurenz,
Dirk"
<Dirk.Laurenz-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org>
Cc: "Oeltze,
Benjamin"
<Benjamin.Oeltze-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: RE: Sm-notify
Date: Sat, 28 Jun 2008 20:33:41 +1000 [thread overview]
Message-ID: <18534.4997.157000.160865@notabene.brown> (raw)
In-Reply-To: message from Laurenz, Dirk on Saturday June 28
On Saturday June 28, Dirk.Laurenz-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org wrote:
> i, the time out is from node a to b seconds, but from node b to a 15 minutes.
> what I saw was, that the handle changed in /var/lib/nfs/rmtab from 0x000002 to 0x000003 although
> the fsid is the same on both nodes.
> how can the 15minute timeout occur?
The number is rmtab (e.g. 0x000002) is like a reference count. The
fact that you sometimes see '2' and sometimes '3' is of no real
interest.
I am correct in interpreting what you say as:
When you fail over from 'a' to 'b', it does so quite quickly, but
when you then fail back from 'b' to 'a', you get a 15 minute
timeout?
If not, please explain in more detail.
If so:
Why exactly are you doing this. It doesn't seem to make sense.
Did 'b' get rebooted in the interim?
It could be that you are hitting the same issue discussed here:
http://linux-nfs.org/pipermail/nfsv4/2008-June/008673.html
and in the surrounding thread.
However this has nothing to do with sm-notify.
NeilBrown
prev parent reply other threads:[~2008-06-28 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 13:33 [PATCH] NFSD: fix use of setsockopt Olga Kornievskaia
2008-06-25 0:50 ` Dean Hildebrand
2008-06-25 19:40 ` J. Bruce Fields
2008-06-25 19:37 ` J. Bruce Fields
2008-06-25 20:44 ` Olga Kornievskaia
2008-06-26 17:14 ` J. Bruce Fields
2008-06-26 17:59 ` Sm-notify Laurenz, Dirk
[not found] ` <FC3FA7C4E1CA2348B5579A68B24556E9DA4AF2946C-KofoAzQUpSBAuK1PVaBULA@public.gmane.org>
2008-06-27 2:22 ` Sm-notify NeilBrown
[not found] ` <46260.192.168.1.70.1214533375.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2008-06-27 6:58 ` Sm-notify Oeltze, Benjamin
2008-06-27 23:44 ` Sm-notify Neil Brown
[not found] ` <18533.31573.855657.391140-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-06-28 7:38 ` Sm-notify Laurenz, Dirk
2008-06-28 10:33 ` Neil Brown [this message]
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=18534.4997.157000.160865@notabene.brown \
--to=neilb@suse.de \
--cc=Benjamin.Oeltze-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org \
--cc=Dirk.Laurenz-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox