Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: eh@dataconnection.com
Cc: nfs@lists.sourceforge.net
Subject: Re: Problem with NLM on Fedora
Date: Wed, 13 Apr 2005 19:43:55 -0400	[thread overview]
Message-ID: <425DAEBB.2000806@RedHat.com> (raw)
In-Reply-To: <9E621559095AA746B22B21CD4FAF99A50A4E76@EDINMAIL1.ad.datcon.co.uk>

eh@dataconnection.com wrote:
> I've just installed Fedora, and am having problems with NFS. 
> 
> What I'm seeing is that NLM requests are not issued to the NFS server 
> (which is a SNAP Server).  Instead the application hangs for about 7 
> seconds, and then returns successfully (i.e. the locks are ostensibly 
> granted).  The delay happens both on locks and unlock requests.  Via 
> tcpdump I see NFS requests/responses, but no RPC calls for NLM.
Could you post a bzip2-ed ethereal trace (meaning
tethereal -w /tmp/dump.pcap; bzip2 /tmp/dump.pcap) of this?

There are some know locking issue with FC3
(see: https://bugzilla.redhat.com/beta/show_bug.cgi?id=150151)
but this appears to be a bit different...

steved.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-04-13 23:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 20:55 Problem with NLM on Fedora eh
2005-04-13 23:43 ` Steve Dickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 10:51 eh
2005-04-20 13:40 ` Neil Horman
2005-04-14 10:05 eh
2005-04-12 19:45 Edward Hibbert

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=425DAEBB.2000806@RedHat.com \
    --to=steved@redhat.com \
    --cc=eh@dataconnection.com \
    --cc=nfs@lists.sourceforge.net \
    /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