linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Łukasz Oleś" <lukasz.oles@open-e.com>
To: linux-nfs@vger.kernel.org
Cc: Artur Piechocki <artur.piechocki@open-e.com>
Subject: Testing sm-notify
Date: Mon, 31 Jan 2011 10:45:01 +0100	[thread overview]
Message-ID: <201101311045.02517.lukasz.oles@open-e.com> (raw)

Hello,

I am using nfs-utils version 1.2.3. I am trying to test sm-notify, I have 2 
test scenarios:

First one:
1 server, 2 clients - client 1 locks file on nfs server, client 2 is trying to 
lock the same file and waiting.  I'm restarting client 1, client 2 locks file.
Everything works fine

Second:
1 server, 1 client - client locks file. I'm restarting server and  client 
should relock file, but I don't know any program which can do it. 

How do you testing this scenario? Can you recommend any program which can 
automaticly lock file again?


Regards,

--
Łukasz Oleś

             reply	other threads:[~2011-01-31  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  9:45 Łukasz Oleś [this message]
2011-01-31 15:43 ` Testing sm-notify J. Bruce Fields

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=201101311045.02517.lukasz.oles@open-e.com \
    --to=lukasz.oles@open-e.com \
    --cc=artur.piechocki@open-e.com \
    --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;
as well as URLs for NNTP newsgroup(s).