mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Orion Poplawski <orion@cora.nwra.com>
To: Samuel Flory <sflory@rackable.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS - IRIX client issues
Date: Wed, 04 Dec 2002 16:47:49 -0700	[thread overview]
Message-ID: <3DEE9425.40204@cora.nwra.com> (raw)
In-Reply-To: <3DEE8EC2.2040305@rackable.com>

Samuel Flory wrote:

> Orion Poplawski wrote:
>
>> Hello -
>>
>>    I was wondering if there were and know NFS issues with IRIX 
>> clients?  I'm seeing a problem where an IRIX 6.5.17m client
>> accessing a linux 2.4.18 (redhat 7.2: -18.7.x) server will hang trying
>> to access a mount.  No traffic appears to make it to the server so it
>> appears to be locked up on the client end, but I don't know why.
>
>
>
>  Can you give a few more details?  Does the nfs share mount, or hang 
> at mounting?  What type of mount are you trying to do? (IE nfs v3 tcp, 
> or v2 udp)
>
>
> PS- Are you certain you aren't running iptables or ipchains? 
> "/etc/init.d/ipchains stop"  Also try mounting with out locking.  
> "mount foo:/foobar /mnt/nfs -onolock"  Have you tried nfs v2? "mount 
> -o nfsvers=2 foo:/foobar /mnt/nfs"
>
>
>
The mount comes up fine and works for quite a while and then crashes. 
 This is under relatively heavy load (tar files being unpacked, data 
files manipulated, etc.).  No iptables/chains.

The mount is automounted,  the resulting mtab entry on IRIX is:

lego:/export/turb3 /data/turb3 nfs vers=3,rw,dev=100007 0 0

I believe the mount is UDP,  I'm not specifying any special options.

I'll look into trying nolock and v2.  SHould I try TCP?

- Orion





  reply	other threads:[~2002-12-04 23:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 22:46 Orion Poplawski
2002-12-04 23:24 ` Samuel Flory
2002-12-04 23:47   ` Orion Poplawski [this message]
2002-12-04 23:54     ` Samuel Flory
2002-12-05  0:26       ` Orion Poplawski
2002-12-18  0:28       ` Orion Poplawski
2002-12-05  5:15     ` Barry K. Nathan
2002-12-05 15:52       ` Orion Poplawski

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=3DEE9425.40204@cora.nwra.com \
    --to=orion@cora.nwra.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    /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

Powered by JetHome