From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Ara.T.Howard" <Ara.T.Howard@noaa.gov>,
Dan Stromberg <strombrg@dcs.nac.uci.edu>,
Jeffrey Layton <jtlayton@poochiereds.net>,
nfs@lists.sourceforge.net
Subject: Re: Linux' NFS locking b0rken?
Date: Thu, 27 May 2004 19:04:37 +0200 [thread overview]
Message-ID: <20040527170437.GA16548@suse.de> (raw)
In-Reply-To: <1085675509.4074.26.camel@lade.trondhjem.org>
On Thu, May 27, 2004 at 12:31:49PM -0400, Trond Myklebust wrote:
> That said, I believe that RHEL-3 at least is returning an error these
> days whenever you try to flock over NFS: I dunno if you are doing this
> at SuSE yet?
We did, on SLES8. Those were some silly third party patches we included
that changed flock to call the lock() function of the underlying FS.
The NFS lock function returns -ENOLCK in this case.
I don't know where this patch came from. Maybe it was GFS related.
I did have to handle a fair share of bug reports because of that.
But I think those broken movemails are not the issue; in fact this
change would actually _fix_ these apps to work over NFS, for the first
time. The only problematic apps would be those mixing flock and fcntl
on a single open file.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-05-27 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 12:23 Linux' NFS locking b0rken? Jeffrey Layton
2004-05-25 12:34 ` Olaf Kirch
2004-05-25 16:42 ` Jeffrey Layton
2004-05-25 17:47 ` Trond Myklebust
2004-05-25 18:56 ` Dan Stromberg
2004-05-25 19:03 ` Trond Myklebust
2004-05-25 19:08 ` Ara.T.Howard
2004-05-25 19:12 ` Trond Myklebust
2004-05-25 21:09 ` Ara.T.Howard
2004-05-25 22:11 ` Trond Myklebust
2004-05-26 7:50 ` Olaf Kirch
2004-05-26 16:04 ` Trond Myklebust
2004-05-27 16:14 ` Olaf Kirch
2004-05-27 16:24 ` Jeffrey Layton
2004-05-27 16:31 ` Trond Myklebust
2004-05-27 17:04 ` Olaf Kirch [this message]
2004-05-28 13:28 ` Ara.T.Howard
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=20040527170437.GA16548@suse.de \
--to=okir@suse.de \
--cc=Ara.T.Howard@noaa.gov \
--cc=jtlayton@poochiereds.net \
--cc=nfs@lists.sourceforge.net \
--cc=strombrg@dcs.nac.uci.edu \
--cc=trond.myklebust@fys.uio.no \
/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.