From: linux-kernel-owner@vger.kernel.org
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: 2.6.X File locking on NFS stil broken
Date: Wed, 9 Jun 2004 22:42:35 +0200 [thread overview]
Message-ID: <20040609204235.GC29969@puettmann.net> (raw)
In-Reply-To: <1086813672.4078.24.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Wed, Jun 09, 2004 at 04:41:12PM -0400, Trond Myklebust wrote:
> That script works fine for me: I haven't seen any hangs on locking in
> any of the 2.6 series kernels so far.
If I mount it with nolock it runs fine too ;-). I have not enough C
knowledge to see whree the bug is.
>
> What does 'rpcinfo -p' show on the client and server?
>
Server :
sslnfs:~# rpcinfo -p
Program Vers Proto Port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 759 status
100024 1 tcp 762 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 32779 nlockmgr
100021 3 udp 32779 nlockmgr
100021 4 udp 32779 nlockmgr
100005 1 udp 901 mountd
100005 1 tcp 904 mountd
100005 2 udp 901 mountd
100005 2 tcp 904 mountd
100005 3 udp 901 mountd
100005 3 tcp 904 mountd
Client:
root@www10:[~] > rpcinfo -p
Program Vers Proto Port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100024 1 udp 938 status
100024 1 tcp 941 status
Ruben
--
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-09 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 19:17 2.6.X File locking on NFS stil broken Ruben Puettmann
2004-06-09 20:41 ` Trond Myklebust
2004-06-09 20:42 ` linux-kernel-owner [this message]
[not found] ` <1086814428.4078.35.camel@lade.trondhjem.org>
[not found] ` <20040609210313.GE29969@puettmann.net>
[not found] ` <1086815623.4078.43.camel@lade.trondhjem.org>
2004-06-09 21:24 ` Ruben Puettmann
2004-06-10 2:58 ` Ryan Anderson
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=20040609204235.GC29969@puettmann.net \
--to=linux-kernel-owner@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox