All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Davis, Jeff (Houston)" <jdavis@hess.com>
To: <neilb@cse.unsw.edu.au>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: round robin dns, multihomed host, nfs mounting issues
Date: Sun, 20 Jul 2003 18:41:16 -0500	[thread overview]
Message-ID: <292E6FA1FCA21C45B614DAC7FBED6D4B874E68@hacssex002.ihess.com> (raw)

Nfs server does not provide routing

It default routes through interface 1. Request was getting to server but =
not back to client

the system seems to be working as I hoped once I upgraded rh80 to nfs =
utils 1.05

Thanks for the help

--------------------------
Jeff Davis
Amerada Hess
Global IT Infrastructure
Technical Computing
Houston, Texas
jdavis@hess.com
713-609-5436 (work)
281-467-9448 (cell)

Sent by BlackBerry Wireless Email

-----Original Message-----
From: Neil Brown <neilb@cse.unsw.edu.au>
To: Davis, Jeff (Houston) <jdavis@hess.com>
CC: nfs@lists.sourceforge.net <nfs@lists.sourceforge.net>
Sent: Sun Jul 20 18:32:19 2003
Subject: Re: [NFS] round robin dns, multihomed host, nfs mounting issues

On Saturday July 19, jdavis@hess.com wrote:
>=20
> Given Neil's comments about possible glibc bug and nfs 1.05, and my =
sense that it is working, is it reasonable for me to think its working?
>=20
> I.e should it work?

Maybe.

It is entirely possible that I mis-diagnosed your problem.  If your
NFS server is the only route between the two subnets, I probably did. =20

However I cannot think of any recent change in nfs-utils that would
affect anything like your problem, but then my memory isn't perfect.

I suggest you test your configuration and if it works, be happy.

When I had the problem I mentioned, I used rpcinfo for testing:

  rpcinfo -u $HOSTNAME mountd 3

If run this on a representative sample of clients, using a
representative sample of server IP address, and it always works, then
I guess your problem has gone away

NeilBrown



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-07-20 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 23:41 Davis, Jeff (Houston) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-22 19:50 round robin dns, multihomed host, nfs mounting issues Jeff Davis
2003-07-19 13:07 Davis, Jeff (Houston)
2003-07-20 23:32 ` Neil Brown
2003-07-18 17:31 Jeff Davis
2003-07-19 10:34 ` Neil Brown

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=292E6FA1FCA21C45B614DAC7FBED6D4B874E68@hacssex002.ihess.com \
    --to=jdavis@hess.com \
    --cc=neilb@cse.unsw.edu.au \
    --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.