All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronald rojas <alsonsdev_mis@dctech.com.ph>
To: nfs@lists.sourceforge.net
Subject: nfs problem: nfs could be mounted and viewed but errors on file opening
Date: Fri, 10 Sep 2004 13:50:37 +0800	[thread overview]
Message-ID: <1094795240.3169.17.camel@roach.aldevinco.com> (raw)

i'm having problems opening my nfs mounted files on the client machine.
Mounting the nfs share on the client goes ok. the user and group
permissions are ok. i could even ls -l and cd into the mounted directory
and subdirectories but when i open a file (cat somefile.txt) i get a
segmentation fault. after that, umounting the nfs share seems to hang.

i noticed this problem when i upgraded the kernel on the client machine
from 2.4 to 2.6. (is there any relation?)

server config:				client config:
nfs-utils version 1.0.1			nfs-utils version 1.0.1
kernel ver. 2.4.18-14			kernel ver. 2.6.8
redhat 8.0 distro			fedora core 1.0

/etc/exports = "/data/revr	192.168.168.1(ro,sync)"
rpcinfo -p localhost on the server:
-bash-2.05b$ /usr/sbin/rpcinfo -p localhost
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32768  status
    391002    2   tcp  32769  sgi_fam
    100011    1   udp    856  rquotad
    100011    2   udp    856  rquotad
    100011    1   tcp    859  rquotad
    100011    2   tcp    859  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp  32775  nlockmgr
    100021    3   udp  32775  nlockmgr
    100021    4   udp  32775  nlockmgr
    100005    1   udp  32776  mountd
    100005    1   tcp  32770  mountd
    100005    2   udp  32776  mountd
    100005    2   tcp  32770  mountd
    100005    3   udp  32776  mountd
    100005    3   tcp  32770  mountd
rpcinfo -p servername run on the client:
[revr@roach revr]$ /usr/sbin/rpcinfo -p 192.168.168.254
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32768  status
    391002    2   tcp  32769  sgi_fam
    100011    1   udp    856  rquotad
    100011    2   udp    856  rquotad
    100011    1   tcp    859  rquotad
    100011    2   tcp    859  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp  32775  nlockmgr
    100021    3   udp  32775  nlockmgr
    100021    4   udp  32775  nlockmgr
    100005    1   udp  32776  mountd
    100005    1   tcp  32770  mountd
    100005    2   udp  32776  mountd
    100005    2   tcp  32770  mountd
    100005    3   udp  32776  mountd
    100005    3   tcp  32770  mountd

the nfs-utils on the client was originally 1.0.6. i tried installing
nfs-utils 1.0.1 but still the same error message. i hope this
information is enough to solve my nfs problem. tia



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2004-09-10  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  5:50 ronald rojas [this message]
2004-09-10 11:22 ` nfs problem: nfs could be mounted and viewed but errors on file opening Steve Dickson
2004-09-10 16:26 ` Trond Myklebust

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=1094795240.3169.17.camel@roach.aldevinco.com \
    --to=alsonsdev_mis@dctech.com.ph \
    --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 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.