From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Łukasz Oleś" <lukasz.oles@open-e.com>
Cc: linux-nfs@vger.kernel.org, Artur Piechocki <artur.piechocki@open-e.com>
Subject: Re: Testing sm-notify
Date: Mon, 31 Jan 2011 10:43:18 -0500 [thread overview]
Message-ID: <20110131154318.GC30447@fieldses.org> (raw)
In-Reply-To: <201101311045.02517.lukasz.oles@open-e.com>
On Mon, Jan 31, 2011 at 10:45:01AM +0100, Łukasz Oleś wrote:
> 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?
I don't understand the question.
One way to test that behavior is correct might be using 2 clients:
client 1 acquires lock, server reboots, then client 2 requests same
lock after reboot. If client 1 managed to reacquire the lock during the
grace period, then client 2's lock request should continue to block.
--b.
prev parent reply other threads:[~2011-01-31 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:45 Testing sm-notify Łukasz Oleś
2011-01-31 15:43 ` J. Bruce Fields [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=20110131154318.GC30447@fieldses.org \
--to=bfields@fieldses.org \
--cc=artur.piechocki@open-e.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lukasz.oles@open-e.com \
/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).