From: Jamie Lokier <jamie@shareable.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: jra@samba.org, andros@citi.umich.edu, linux-fsdevel@vger.kernel.org
Subject: Re: file leases
Date: Wed, 22 Sep 2004 14:36:06 +0100 [thread overview]
Message-ID: <20040922133606.GA27338@mail.shareable.org> (raw)
In-Reply-To: <20040922224119.6f73909b.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> > This was triggered by creating 3rd.jpg (copied locally from
> > elsewhere). Then viewing it in Internet Explorer on the Windows ME
> > client. Then closing IE, and trying to copy the file locally.
>
> Closing IE, won't cause the Windows client to release the lease, it tries
> to hold it as long as possible so that it knows its local cached copy of
> the file is still correct.
Yes, that's what I assumed.
> > At about 11:50:49 I expect to see linux_oplock_receive_message and
> > then linux_release_kernel_oplock -- because I see these at times when
> > there's no stall -- but I *don't* see either in the Samba log after
> > this point:
>
> So this is not consistent i.e. it works as expected most of the time?
It's not consistent. Most of the time it stalls with oplocks enabled
in Samba.
Specifically: If I have been viewing or editing a file in Windows,
then most of the time oplocks viewing or editing the same file on the
server stalls. I thought it was stalling every time.
However when I did these tests today with the "cp" command, I was
surprised to see it not stalling sometimes. So it is inconsistent.
> > Perhaps more worryingly, there is no communication with Windows ME, so
> > Windows ME may still think it has the oplock. 20 minutes later, after
> > viewing the file a couple more times in ME, and after editing it
> > locally, there are no further messages with "oplock" or "linux" in the
> > Samba log.
>
> This makes sense as Windows still thinks it has the oplock.
>
> > It looks like either:
> >
> > (1) Linux leases aren't working: they're not signalling Samba.
> >
> > (2) or, Samba is not interfacing with Linux leases properly, so
> > is missing the signal.
>
> Either is possible. Is this a standard kernel.org 2.6.8 kernel and
> a standard samba 3.0.6 - or are these distribution versions?
Gentoo versions.
Kernel is gentoo-dev-sources-2.6.8, which is Linux 2.6.8 plus a few small
patches that don't touch locks.c or anything that looks relevant.
Samba is samba-3.0.6-r3, again none of the small patches looks relevant.
-- Jamie
next prev parent reply other threads:[~2004-09-22 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-09-22 18:59 ` Jeremy Allison
2004-09-22 21:43 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2004-09-21 15:07 William A.(Andy) Adamson
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=20040922133606.GA27338@mail.shareable.org \
--to=jamie@shareable.org \
--cc=andros@citi.umich.edu \
--cc=jra@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.