From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Robert W. Fuller" <garbageout@sbcglobal.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs file locking broken
Date: Tue, 17 Oct 2006 14:40:55 -0400 [thread overview]
Message-ID: <1161110455.5559.16.camel@lade.trondhjem.org> (raw)
In-Reply-To: <45352148.4020706@sbcglobal.net>
On Tue, 2006-10-17 at 14:30 -0400, Robert W. Fuller wrote:
> Robert W. Fuller wrote:
> > I tried to upgrade from 2.6.16.27 to 2.6.17.13. I have also tried
> > 2.6.18.1. I discovered NFS file locking no longer works between a Linux
> > client and an OpenBSD server. For example, gtk-gnutella gets the
> > following error:
> >
> > 06-10-14 15:50:19 (WARNING): fcntl(8, F_SETLK, ...) failed for
> > "/home/edison/.gtk-gnutella/gtk-gnutella.pid": Permission denied
> >
> > gpg hangs waiting for a lock for ~/.gnupg/random_seed
>
> Maybe the thing to do is to Cc: the NFS guy on this? Anybody else have
> any suggestions?
>
> Is there a known fundamental change in the Linux NFS client that would
> break file locking between a Linux NFS client and an OpenBSD-3.8 NFS
> server? Is OpenBSD-3.8 somehow broken with respect to new behavior in
> the Linux NFS client?
>
> This is very reproducible. File locking works with 2.6.16.27. Sometime
> thereafter it ceased to work. There are no configuration changes to
> /etc or anything like that.... For me, it's a simple matter of choosing
> a working kernel from the GRUB menu or a broken kernel.
File locking works fine for me, both against Linux boxes and others. I
don't have any OpenBSD servers to test, though.
Have you tried using something like ethereal/wireshark in order to sniff
the wire?
Cheers,
Trond
prev parent reply other threads:[~2006-10-17 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 20:17 Robert W. Fuller
2006-10-17 18:30 ` Robert W. Fuller
2006-10-17 18:40 ` Trond Myklebust [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=1161110455.5559.16.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=garbageout@sbcglobal.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®