From: Nils Goroll <slink-fLMQ21Bj+IYb1SvskN2V4Q@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Re: nfs4 locks: What happens when a lease can't get renewed?
Date: Thu, 17 Jun 2010 12:08:56 +0200 [thread overview]
Message-ID: <4C19F438.6060800@schokola.de> (raw)
In-Reply-To: <4C12A779.6010005-fLMQ21Bj+IYb1SvskN2V4Q@public.gmane.org>
Hi,
I am reposting my question because I feel it is quite substantial. IMHO, some
mechanism to ensure data integrity is needed for "lost locks".
On 06/11/10 11:15 PM, Nils Goroll wrote:
> Hi,
>
> I wonder what happens if a lock on nfs4 has been acquired by an application (for
> instance, using fcntl(fd, F_SETLK, F_WRLCK)) and the lock can't be RENEWed, for
> instance due to a network outage preventing communication between the client and
> the server.
>
> I would have thought that some notification mechanism was useful, for instance
> my means of delivery of a signal as set using F_SETOWN / F_SETSIG for leases.
>
> I would highly appreciate helpful pointers should this question have already
> been discussed of if there exists any other helpful documentation on it.
>
> Thank you,
>
> Nils
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-06-17 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 21:15 nfs4 locks: What happens when a lease can't get renewed? Nils Goroll
[not found] ` <4C12A779.6010005-fLMQ21Bj+IYb1SvskN2V4Q@public.gmane.org>
2010-06-17 10:08 ` Nils Goroll [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=4C19F438.6060800@schokola.de \
--to=slink-flmq21bj+iyb1svskn2v4q@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