From: "William A.(Andy) Adamson" <andros@citi.umich.edu>
To: jamie@shareable.org
Cc: andros@citi.umich.edu, sfr@canb.auug.org.au,
linux-fsdevel@vger.kernel.org
Subject: Re: file leases
Date: Tue, 21 Sep 2004 11:07:26 -0400 [thread overview]
Message-ID: <20040921150726.7D58A1BBB6@citi.umich.edu> (raw)
ah. i have performed similar tests with nfsd and delegations. i'll open a file
for READ locally on a version 4 nfsd exported portion of the file system, and
request a lease via fcntl_setlease() setting up a signal handler to handle the
break_lease callback. then, i'll open the same file for WRITE from an nfs
version 4 client. the lease on the local file is broken within 1-2 seconds,
and then nfs client WRITE is serviced. if you want, i can send the source to
the test programs to set a lease.
-->Andy
--------jamie@shareable.org said -----------
Eh? There's only one client, and it's idle. Presumably it's holding
an oplock.
When I want to edit a file directly on the server, opening for write
stalls for a long time. Presumably the lease causes Samba to send a
break_lease to the _one_ client. Being an idle client that's not
holding the file open, it should respond immediately to break_lease,
and then Samba should let me open the file locally.
That's how leases are supposed to work, but something in that whole
arrangement isn't working properly. Samba is 3.0.6-r3, kernel is
2.6.8 (both gentoo versions).
next reply other threads:[~2004-09-21 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 15:07 William A.(Andy) Adamson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-20 20:21 PATCH [0/10] lease interfaces for version 4 NFSD William A.(Andy) Adamson
2004-09-20 20:27 ` file leases Jamie Lokier
2004-09-20 20:34 ` William A.(Andy) Adamson
2004-09-21 3:21 ` Stephen Rothwell
2004-09-21 8:40 ` Jamie Lokier
2004-09-21 12:16 ` William A.(Andy) Adamson
2004-09-21 12:44 ` Jamie Lokier
2004-09-21 20:30 ` Jeremy Allison
2004-09-22 11:32 ` Jamie Lokier
2004-09-22 12:41 ` Stephen Rothwell
2004-09-22 13:36 ` Jamie Lokier
2004-09-22 18:59 ` Jeremy Allison
2004-09-22 21:43 ` Jamie Lokier
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=20040921150726.7D58A1BBB6@citi.umich.edu \
--to=andros@citi.umich.edu \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).