From: Neil Brown <neilb@suse.de>
To: "Oeltze,
Benjamin"
<Benjamin.Oeltze-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org>
Cc: "Laurenz,
Dirk"
<Dirk.Laurenz-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: RE: Sm-notify
Date: Sat, 28 Jun 2008 09:44:21 +1000 [thread overview]
Message-ID: <18533.31573.855657.391140@notabene.brown> (raw)
In-Reply-To: message from Oeltze, Benjamin on Friday June 27
On Friday June 27, Benjamin.Oeltze-/ixSogHR0HOS/tZ4Wjpou0EOCMrvLtNR@public.gmane.org wrote:
> Hi,
> maybe I can specify Dirks question.
Thanks.
>
> We are trying to set up a NFS Cluster and want to use sm-notify to inform the Clients if the Server has failed over.
> We have found a Howto that says: sm-notify uses files under /var/lib/nfs/sm to determine the Clients it has to inform.
> Our Problem is, that ther are no files in this place even if we connet with a client. Is there anything we have forgotten?
Files do not get created in /var/lib/nfs/sm until the client tried to
get a lock on some file (or part of a file). Then the file is
created.
Some minutes after the last lock is dropped, the file should be
removed (though I recall there were some issues related to that, it
might depend on exactly which kernel you are running).
If no file locking is involved, there is no need to inform the client
of failover. They will transparently start accessing the new server
through the old IP address, possible after a short timeout.
NeilBrown
next prev parent reply other threads:[~2008-06-27 23:44 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 ` Neil Brown [this message]
[not found] ` <18533.31573.855657.391140-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-06-28 7:38 ` Sm-notify Laurenz, Dirk
2008-06-28 10:33 ` Sm-notify Neil Brown
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=18533.31573.855657.391140@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