Re: NFS Failover

Thx for reply.
How do I check portmap is running on port 111? My service file has port
111 defined (sunrpc) and I can ps for portmap daemon. Is that good
enough? I would assume NFS wouldn't run first place (before failover to
other server). Is that correct?

Thx


ynotssor wrote:
<pechoi@xxxxxxx> wrote in message
news:1153422415.020247.16300@xxxxxxxxxxxxxxxxxxxxxxxxxxx

How is NFS inplementation different in redhat compared to Solaris? A
dude (works at Sun) said NFS don't care about filehandle if a
namespace is exported read-only. I "dd" one disk to another (same
inode and generation number). I mounted via NFS read-only, and disks
are mounted read-only on local as well. However, I am still getting
stale filehandle error. I guess redhat (linux) is different than
Solaris. I saw ip packets (using ethereal. please let me know if
anyone knows how to print generation number easily) and I noticed
that inode and generation numbers are same but filesystem number is
different. How does NFS in linux get filesystem number?

Do you have portmap (a.k.a. sunrpc) running on port 111? It's necessary when
using NFS.

/etc/init.d/portmap {start|stop|status|restart|reload|condrestart}

.

Relevant Pages

  • Re: nfsd support for tcp_wrapper -> General RPC solution
    ... > and whenever portmap receives the RPC service registration from the ... > script passing it the port number where the service has registered. ... > and the overhead is minimal: only a call to the TCP Wrapper library ... In fact because afaik NFS always uses a well known port, ...
    (FreeBSD-Security)
  • Re: NFS Failover
    ... How do I check portmap is running on port 111? ... I would assume NFS wouldn't run first place (before failover to ... Do you have portmap (a.k.a. sunrpc) running on port 111? ...
    (linux.redhat)
  • Re: nfsd support for tcp_wrapper -> General RPC solution
    ... >> In fact because afaik NFS always uses a well known port, ... >> portmapper for NFS is just a formality. ... > to portmap, it puts firewall rules to block access to the port. ...
    (FreeBSD-Security)
  • Re: nfsd support for tcp_wrapper -> General RPC solution
    ... > service to a tcp/udp port. ... > don't need portmap to brute force finding out where a remote ... the brute force portscan will have no success. ... > portmapper for NFS is just a formality. ...
    (FreeBSD-Security)
  • Re: sunrpc - post two for me today...
    ... > I ran nmap on it and found that sunrpc keeps showing up. ... and nfs is turned off. ... > thier problem was fixed by turning portmap off...). ... then the currently running portmap must be ...
    (comp.os.linux.networking)