nfs problem

nfs problem

[george drossos]

I'm a student in South Bank University London and i,m working on a project 
"distibuted and parallel processing in Linux".
I tried to set up NFS(i have 1 server and 2 clients).
My kernel version is 2.4.18-3 and i installed red.hat 7.3.I didn't install 
any other operation system.
I check that nfs is running on the server(all the daemons as start-up 
scripts)and i ckeck that nfs is running on the clients as well.
I edit /etc/exports i wrote the directory that i want to export and the 
destination hosts.
About the clients,the mount version is 2.10n,nfs daemons are running.
I red the file /proc/filesystems if nfs was there,it wasn't but appeared by 
typing insmod nfs.I check again the services by typing rpcinf -p and 
everything was ok.
When i try to mount the remote directory i have error message:
    mount:RPC:Port mapper failure-RPC:Unable to receive

I checked again that NFS was running in three machines and afterwards i 
typed on each client:
                      rpcinfo -p servername
the error message was:
  rpcinfo:can't contact portmapper:RPC remote system error:Connection   
refused

Also i want to say in the case that there is a routing problem,i ping the 
machines and everything is ok.The only problem that i have until now is that 
i cannot connect the clients with the university's network.When i ping the 
default gateway (from the clients) says Network is unreachable.In the case 
of server(has 2 network cards) i ping everything and the university network 
is reachable.

I would really appreciate replying and i'm really looking forward your 
suggestions and advices.

                       George Drossos


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com



-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

NFS problem

[Suresh Chadive]

There has been a problem in mounting the directory
on the client.

PROBLEM :-
----------
If the command :
  $ mount serverIPaddress:/home /home
is issued, then the output is
  mount: RPC: Timed out


INFO THAT MAY BE USEFUL :-
-------------------------

SERVER SIDE :

  $ rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    391002    2   tcp   1025  sgi_fam
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp   1027  nlockmgr
    100021    3   udp   1027  nlockmgr
    100021    4   udp   1027  nlockmgr
    100011    1   udp    755  rquotad
    100011    2   udp    755  rquotad
    100011    1   tcp    758  rquotad
    100011    2   tcp    758  rquotad
    100005    1   udp   1028  mountd
    100005    1   tcp   1030  mountd
    100005    2   udp   1028  mountd
    100005    2   tcp   1030  mountd
    100005    3   udp   1028  mountd
    100005    3   tcp   1030  mountd
    100024    1   udp   1029  status
    100024    1   tcp   1031  status



CLIENT SIDE:

    $  rpcinfo -p
   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

Here, I explicitly run rpc.lockd (on client)
but still, I do not see lock daemon (nslockmanager or some thing of that
sort) ! Any clue?
---------------------------------------------------

Please, give some way to sort it out...

-suresh


----------------------
SURESH CHADIVE

V Yr,
Dual degree Programme

H9, #319,
Indian Instt. of Technology,
Bombay

e-mail :  csuresh@iitbombay.org







-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: NFS problem

[Joseph L. Hood]

Problems I've run into getting NFS going are IPChains firewall rules
(IPTables logging is a little less cryptic) and not having portmap running
on the client.  Also, try "rpcinfo -p <server>"  from the client, or
"rpcinfo -u <server> nfs" to see what the client can see.

Additionally, see if you can nfs mount the shared directories from the
server itself, to make sure they are really shared.

Joe

On Wed, 21 Aug 2002, Suresh Chadive wrote:

> 
> 
> There has been a problem in mounting the directory
> on the client.
> 
> PROBLEM :-
> ----------
> If the command :
>   $ mount serverIPaddress:/home /home
> is issued, then the output is
>   mount: RPC: Timed out
> 
> 
> INFO THAT MAY BE USEFUL :-
> -------------------------
> 
> SERVER SIDE :
> 
>   $ rpcinfo -p
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     391002    2   tcp   1025  sgi_fam
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100021    1   udp   1027  nlockmgr
>     100021    3   udp   1027  nlockmgr
>     100021    4   udp   1027  nlockmgr
>     100011    1   udp    755  rquotad
>     100011    2   udp    755  rquotad
>     100011    1   tcp    758  rquotad
>     100011    2   tcp    758  rquotad
>     100005    1   udp   1028  mountd
>     100005    1   tcp   1030  mountd
>     100005    2   udp   1028  mountd
>     100005    2   tcp   1030  mountd
>     100005    3   udp   1028  mountd
>     100005    3   tcp   1030  mountd
>     100024    1   udp   1029  status
>     100024    1   tcp   1031  status
> 
> 
> 
> CLIENT SIDE:
> 
>     $  rpcinfo -p
>    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
> 
> Here, I explicitly run rpc.lockd (on client)
> but still, I do not see lock daemon (nslockmanager or some thing of that
> sort) ! Any clue?
> ---------------------------------------------------
> 
> Please, give some way to sort it out...
> 
> -suresh
> 
> 
> ----------------------
> SURESH CHADIVE
> 
> V Yr,
> Dual degree Programme
> 
> H9, #319,
> Indian Instt. of Technology,
> Bombay
> 
> e-mail :  csuresh@iitbombay.org
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> 




-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: NFS problem

[Patrick O'Reilly]

First, a good page to check is:

http://ftp.belnet.be/packages/redhat/redhat-7.1-en/doc/HOWTOS/other-formats/
html/NFS-HOWTO/server.html#SERVICESTART

to get your services started.  If you are using Linux, you can also try
this. Issue the command:

chkconfig --list

and a list of services will scroll by.  Check to see that portmap, nfs and
nfslock are 'on' on levels 3, 4, and 5.  If not, issue the commands:

chkconfig --level 345 portmap on
chkconfig --level 345 nfs on
chkconfig --level 345 nfslock on

and these should be turned on, and will start on reboot.  Try this on the
client and see what happens if it looks like it will help.  Good luck.

Patrick

----- Original Message -----
From: "Suresh Chadive" <n8d11007@ccs.iitb.ac.in>
To: <nfs@lists.sourceforge.net>
Sent: Tuesday, August 20, 2002 7:01 PM
Subject: [NFS] NFS problem


>
>
> There has been a problem in mounting the directory
> on the client.
>
> PROBLEM :-
> ----------
> If the command :
>   $ mount serverIPaddress:/home /home
> is issued, then the output is
>   mount: RPC: Timed out
>
>
> INFO THAT MAY BE USEFUL :-
> -------------------------
>
> SERVER SIDE :
>
>   $ rpcinfo -p
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     391002    2   tcp   1025  sgi_fam
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100021    1   udp   1027  nlockmgr
>     100021    3   udp   1027  nlockmgr
>     100021    4   udp   1027  nlockmgr
>     100011    1   udp    755  rquotad
>     100011    2   udp    755  rquotad
>     100011    1   tcp    758  rquotad
>     100011    2   tcp    758  rquotad
>     100005    1   udp   1028  mountd
>     100005    1   tcp   1030  mountd
>     100005    2   udp   1028  mountd
>     100005    2   tcp   1030  mountd
>     100005    3   udp   1028  mountd
>     100005    3   tcp   1030  mountd
>     100024    1   udp   1029  status
>     100024    1   tcp   1031  status
>
>
>
> CLIENT SIDE:
>
>     $  rpcinfo -p
>    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
>
> Here, I explicitly run rpc.lockd (on client)
> but still, I do not see lock daemon (nslockmanager or some thing of that
> sort) ! Any clue?
> ---------------------------------------------------
>
> Please, give some way to sort it out...
>
> -suresh
>
>
> ----------------------
> SURESH CHADIVE
>
> V Yr,
> Dual degree Programme
>
> H9, #319,
> Indian Instt. of Technology,
> Bombay
>
> e-mail :  csuresh@iitbombay.org
>
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: NFS problem

[Suresh Chadive]

Thank you very much for the support I got. It is
really timely help to me.

The suggestions helped me in making a breakthrough,
however, still the problem persists. I think I have
rounded off the critical thing now.

1) The portmap, nfs, nfslock were off for the levels 345
   I rectified it. Now the client also shows all the important
   daemons running.

2) - rpcinfo -p on server and client now give all the daemons.
    ----------------------------------------------------------
   - also, the command:

	$ rpcinfo -p server
     produces the same input as obtained on the server (issuing
     ----------------------------------------------  rpcinfo -p)

    Interesting part is

	$ rpcinfo -u server nfs
        $ rpcinfo -u server portmap

    are getting timed out !!!!. They produce (for the case of portmap):

                rpcinfo: RPC: Port mapper failure - RPC: Timed out
		program 100000 is not available


    Will this give any clue to the problem?


 3) The mounting on to the server itself is successful !
    Is it that server side is absolutely OK?


Eagerly looking for the final shot...


Best regards,
-suresh


----------------------
SURESH CHADIVE

V Yr,
Dual degree Programme

H9, #319,
IIT Bombay

e-mail :  csuresh@iitbombay.org





-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: NFS problem

[Patrick O'Reilly]

>From what I see from the man page of rpcinfo, try a

rpcinfo -s <server>

from the client and see what services are there and what program number they
are associated with.  Sure enough my portmap service is program 100000, just
as yours complains about not finding.  If the services are showing up when
you issue rpcinfo -p from the server, they should be there and show program
number from the above command.  If you generically say:

rpcinfo -u <server> portmap

it may automatically look for program number 100000 and all I can think of
is that your portmap service is not running under that program number.  Not
sure why it wouldn't be.  If it isn't then substitute the program number for
portmap in the above command and see what you find.

Patrick

----- Original Message -----
From: "Suresh Chadive" <n8d11007@ccs.iitb.ac.in>
To: <nfs@lists.sourceforge.net>
Sent: Wednesday, August 21, 2002 1:45 PM
Subject: Re: [NFS] NFS problem


>
> Thank you very much for the support I got. It is
> really timely help to me.
>
> The suggestions helped me in making a breakthrough,
> however, still the problem persists. I think I have
> rounded off the critical thing now.
>
> 1) The portmap, nfs, nfslock were off for the levels 345
>    I rectified it. Now the client also shows all the important
>    daemons running.
>
> 2) - rpcinfo -p on server and client now give all the daemons.
>     ----------------------------------------------------------
>    - also, the command:
>
> $ rpcinfo -p server
>      produces the same input as obtained on the server (issuing
>      ----------------------------------------------  rpcinfo -p)
>
>     Interesting part is
>
> $ rpcinfo -u server nfs
>         $ rpcinfo -u server portmap
>
>     are getting timed out !!!!. They produce (for the case of portmap):
>
>                 rpcinfo: RPC: Port mapper failure - RPC: Timed out
> program 100000 is not available
>
>
>     Will this give any clue to the problem?
>
>
>  3) The mounting on to the server itself is successful !
>     Is it that server side is absolutely OK?
>
>
> Eagerly looking for the final shot...
>
>
> Best regards,
> -suresh
>
>
> ----------------------
> SURESH CHADIVE
>
> V Yr,
> Dual degree Programme
>
> H9, #319,
> IIT Bombay
>
> e-mail :  csuresh@iitbombay.org
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

NFS Problem

[Victor Zamora]

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]



Hi,

   I have configured a NFS server and a client in a network (two separate machines). This runs over a linux 2.4.18 kernell (mini slackware version). 
    On the server side I've exported a path to the oder specific machine (with its IP), and I've executed portmap, nfsd, and mountd daemons. I've also executed exportfs -ra so to make sure that the kernell knows about the nfs export I want to do.
    On the client side I've run portmap daemon, but when I run the mount it appears a message from the server saying "Permison denied".

    I've tryied changing the way I exported the filepath and how I mounted the NFS from the client, but I couldn't make it.

   If anyone has any idea of what is causing this permison denial, please don't doubt about geting me know it. 
  I'll be very gratefull to any suggestion.

                                                             Thanks for your time,
                                                                                        Victor.-
   

[-- Attachment #2: Type: text/html, Size: 2576 bytes --]

NFS Problem

[Muhammad Sibtain Bashir]

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

Dear sir 

i am using NFS server , instead of using the domain names i am using the IP addresses of my clients machines 
 the file /etc/export looks like

/google                     203.215.160.2(rw)
/345                        203.215.160.2(rw)
/mnt/cdrom              203.215.160.2(rw)

now when i mount the directories on my client machine it get mounted okay and i can read any file in the mounted directories but as above i have given the write permision as well ,but i cant write any thing  and this message show   * permission denied*.


waiting for response plz .

regards

Muhammad Sibtain

[-- Attachment #2: Type: text/html, Size: 1883 bytes --]

RE: NFS Problem

[Jose Santiago]

What are the permissions on the directories that you are trying to write 
to via NFS? What user is trying to do the write? Be aware, that root 
maps to user nobody via NFS unless you root_squash.

 > now when i mount the directories on my client machine it get mounted
 > okay and i can read any file in the mounted directories but as above i
 > have given the write permision as well ,but i cant write any thing and
 > this message show   * permission denied*.



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

nfs problem

[vadivel vadi]

hai

    in my nfs server the rpc mountd service is stopped every 1 hour
what is the proper can u solve it.and also i want t know how many
system can connect thro nfs if a data is about 200GB i want to know it
immediately.i thick u can solve my problem.

             regards
            vadivel


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

nfs problem

[Arnau Bria]

Hi,

I have a new nfs server with this env:

[root@cdf-nfsserver root]# uname -a
Linux cdf-nfsserver 2.4.21-32.0.1.ELsmp #1 SMP Wed May 25
15:42:26 CDT 2005 i686 i686 i386 GNU/Linux 

[root@cdf-nfsserver root]#rpm -qa|grep nfs nfs-utils-1.0.6-33EL
redhat-config-nfs-1.0.13-6

[root@cdf-nfsserver root]# cat /etc/redhat-release
Scientific Linux release 3.0.5 (Fermi)

and a client with same redhat-release, nfs-utils package version and
diff kernel:

[root@cdf-bcnhead init.d]# uname -a
Linux cdf-bcnhead 2.4.21-47.0.1.ELsmp #1 SMP Thu Oct 19
10:46:05 CDT 2006 i686 i686 i386 GNU/Linux

I'm noticing that communication between them is very slow, but they
share switch, so shouldn't be bad. No errors packets reported in
ifconfig:
RX packets:219163615 errors:0 dropped:0 overruns:0 frame:0
TX packets:264718776 errors:0 dropped:0 overruns:0 carrier:0


Looking into logs I found this messages in server (cdf-nfsserver)

cdf-nfsserver rpc.statd[3294]: Received erroneous SM_UNMON request from
IP_SERVER for IP_CLIENT 

cdf-nfsserver rpc.statd[3294]: Received erroneous SM_UNMON request from
IP_SEVER for IP_CLIENT

and in the client: (cdf-bcnhead)

cdf-bcnhead rpc.statd[11731]: Received erroneous SM_UNMON request from
IP_CLIENT for IP_SERVER

cdf-bcnhead rpc.statd[11731]: Received erroneous SM_UNMON request from
IP_CLIENT for IP_SERVER

*I have modified values of IP_SERVER-IP_CLIENT*

and looking into client's dmesg I find lots of connection lost
messages:

nfs: server IP_SERVER not responding, still trying
nfs: server IP_SERVER OK

and nothing in server.


As I don't know if the error come from server/client, I've checked Nfs
server processes:

[root@cdf-nfsserver root]# uptime
 11:05:05  up 1 day, 23:09,  1 user,  load average: 0.00, 0.02, 0.00
[root@cdf-nfsserver root]# ps -ef|grep nfs
root      2931     1  0 Jan23 ?        00:12:31 [nfsd]
root      2932     1  0 Jan23 ?        00:12:08 [nfsd]
root      2933     1  0 Jan23 ?        00:11:27 [nfsd]
root      2934     1  0 Jan23 ?        00:12:00 [nfsd]
root      2935     1  0 Jan23 ?        00:12:40 [nfsd]
root      2936     1  0 Jan23 ?        00:11:12 [nfsd]
root      2937     1  0 Jan23 ?        00:11:59 [nfsd]
root      2938     1  0 Jan23 ?        00:12:27 [nfsd]

It is up for one day, and nfsd processes have consumed more than 12
minuts, is this normal?


First google search pointed me to statd directory's permits:

# ls -lsad /var/lib/nfs/statd
   4 drwx------    4 rpcuser  rpcuser      4096 Jan 17
10:19 /var/lib/nfs/statd

but seems correct in both server and client.

Second search recommends a downgrade of nfs-utils, but before doing so,
I'd like to confirm that this is the only solution.

This is server conf:
# cat /etc/exports
/home/cdfcaf    NET.0/255.255.252.0(rw,async,no_root_squash)
/home/cdfsoft   NET.0/255.255.252.0(rw,async,no_root_squash)
/home/cafmon    NET.0/255.255.252.0(rw,async,no_root_squash)
/home/sam       NET.0/255.255.252.0(rw,async,no_root_squash)

and client uses autofs:

# cat /etc/auto.master
/home /etc/auto.home --timeout=600

# cat /etc/auto.home
cdfcaf          -rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/cdfcaf
cdfsoft         -rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/cdfsoft
sam             -rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/sam
cafmon          -rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/cafmon


Anyone knows where is the source of this problem?

Thanks in advance,
Arnau

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

nfs problem

[Arnau Bria]

Hi,

I have a new nfs server with this env:

[root@cdf-nfsserver root]# uname -a
Linux cdf-nfsserver 2.4.21-32.0.1.ELsmp #1 SMP Wed May 25
15:42:26 CDT 2005 i686 i686 i386 GNU/Linux 

[root@cdf-nfsserver root]#rpm -qa|grep nfs nfs-utils-1.0.6-33EL
redhat-config-nfs-1.0.13-6

[root@cdf-nfsserver root]# cat /etc/redhat-release
Scientific Linux release 3.0.5 (Fermi)

and a client with same redhat-release, nfs-utils package version and
diff kernel:

[root@cdf-bcnhead init.d]# uname -a
Linux cdf-bcnhead 2.4.21-47.0.1.ELsmp #1 SMP Thu Oct 19
10:46:05 CDT 2006 i686 i686 i386 GNU/Linux

I'm noticing that communication between them is very slow, but they
share switch, so shouldn't be bad. No errors packets reported in
ifconfig:
RX packets:219163615 errors:0 dropped:0 overruns:0 frame:0
TX packets:264718776 errors:0 dropped:0 overruns:0 carrier:0


Looking into logs I found this messages in server (cdf-nfsserver)

cdf-nfsserver rpc.statd[3294]: Received erroneous SM_UNMON request from
IP_SERVER for IP_CLIENT 

cdf-nfsserver rpc.statd[3294]: Received erroneous SM_UNMON request from
IP_SEVER for IP_CLIENT

and in the client: (cdf-bcnhead)

cdf-bcnhead rpc.statd[11731]: Received erroneous SM_UNMON request from
IP_CLIENT for IP_SERVER

cdf-bcnhead rpc.statd[11731]: Received erroneous SM_UNMON request from
IP_CLIENT for IP_SERVER

*I have modified values of IP_SERVER-IP_CLIENT*

and looking into client's dmesg I find lots of connection lost
messages:

nfs: server IP_SERVER not responding, still trying
nfs: server IP_SERVER OK

and nothing in server.


As I don't know if the error come from server/client, I've checked Nfs
server processes:

[root@cdf-nfsserver root]# uptime
 11:05:05  up 1 day, 23:09,  1 user,  load average: 0.00, 0.02, 0.00
[root@cdf-nfsserver root]# ps -ef|grep nfs
root      2931     1  0 Jan23 ?        00:12:31 [nfsd]
root      2932     1  0 Jan23 ?        00:12:08 [nfsd]
root      2933     1  0 Jan23 ?        00:11:27 [nfsd]
root      2934     1  0 Jan23 ?        00:12:00 [nfsd]
root      2935     1  0 Jan23 ?        00:12:40 [nfsd]
root      2936     1  0 Jan23 ?        00:11:12 [nfsd]
root      2937     1  0 Jan23 ?        00:11:59 [nfsd]
root      2938     1  0 Jan23 ?        00:12:27 [nfsd]

It is up for one day, and nfsd processes have consumed more than 12
minuts, is this normal?


First google search pointed me to statd directory's permits:

# ls -lsad /var/lib/nfs/statd
   4 drwx------    4 rpcuser  rpcuser      4096 Jan 17
10:19 /var/lib/nfs/statd

but seems correct in both server and client.

Second search recommends a downgrade of nfs-utils, but before doing so,
I'd like to confirm that this is the only solution.

This is server conf:
# cat /etc/exports
/home/cdfcaf    NET.0/255.255.252.0(rw,async,no_root_squash)
/home/cdfsoft   NET.0/255.255.252.0(rw,async,no_root_squash)
/home/cafmon    NET.0/255.255.252.0(rw,async,no_root_squash)
/home/sam       NET.0/255.255.252.0(rw,async,no_root_squash)

and client uses autofs:

# cat /etc/auto.master
/home /etc/auto.home --timeout=600

# cat /etc/auto.home
cdfcaf          -rw,hard,intr,async,rsize=8192,wsize=8192
IP_SERVER:/home/cdfcaf cdfsoft
-rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/cdfsoft
sam             -rw,hard,intr,async,rsize=8192,wsize=8192
IP_SERVER:/home/sam cafmon
-rw,hard,intr,async,rsize=8192,wsize=8192 IP_SERVER:/home/cafmon


Anyone knows where is the source of this problem?

Thanks in advance,
Arnau

PS: sorry to admins, I used a non subscribed account for my first
post :-(

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: nfs problem

[Arnau Bria]

On Thu, 25 Jan 2007 15:31:53 +0100
Arnau Bria wrote:

> [root@cdf-nfsserver root]# cat /etc/redhat-release
> Scientific Linux release 3.0.5 (Fermi)
I found a broken autofs and nfs-utils in this distro.

Going to upgrade to see what happen.

Cheers,
Arnau

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs