All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Busch <bbusch@biochem.mpg.de>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: NFS@lists.sourceforge.net
Subject: Re: NFS mount problem (2000 NFS filesystems) of linux clients to a solaris server
Date: Fri, 09 Mar 2007 13:16:24 +0100	[thread overview]
Message-ID: <45F15018.1060804@biochem.mpg.de> (raw)
In-Reply-To: <EXNANE01FRaqbC8wSA10000007f@exnane01.hq.netapp.com>

Talpey, Thomas wrote:




Hello  Tom


Thank you very much for your help.
I was able to mount the 2000 NFS files after your modifications
via:

for i in `seq 1 2000`
do
     mount   -t nfs -o intr,hard,tcp  solaris10-02:/fs/DISK/disk$i  =

/fs/solaris10-02/DISK/disk$i
    sleep  1
 done


But , if i remove the sleep command the

nfs bindresvport: Address already in use

error appears again.

On solaris and sgi clients the above command works correctly without the =

sleep command.

So the machine takes about 1 hour to mount all nfs filesystems.

Any idea?

Best wishes

Bernhard




> At 07:42 AM 3/8/2007, Bernhard Busch wrote:
>   =

>> It is possible to export these 2000 filesystems on the server (sun solar=
is)
>> and  to  mount these 2000 nfs filesystem on sgi and solaris
>> clients without any problems.
>>
>>
>> On Linux Clients (SLES10, Suse10.2)  i get =

>> error messages like the following ones:
>>
>> nfs bindresvport: Address already in use
>> nfs bindresvport: Address already in use
>> nfs bindresvport: Address already in use
>> mount: solaris10-02:/fs/DISK/disk1998: can't read superblock
>> mount: solaris10-02:/fs/DISK/disk1999: can't read superblock
>> mount: solaris10-02:/fs/DISK/disk2000: can't read superblock
>>     =

>
> You need to increase the number of ports available on the Linux NFS
> client.
>
> echo 65535 >/proc/sys/sunrpc/max_resvport
>
> This will raise it to the maximum, you could use smaller values but
> because you are creating so many mounts, that would quite possibly
> start to collide with other reserved ports.
>
> In fact, you might want to set /proc/sys/sunrpc/min_resvport to
> something large (32768), also in order to avoid collisions. However
> that in turn might require reconfiguring some of your NFS servers to
> accept "nonprivileged" ports (Linux server export option "insecure",
> others see documentation).
>
> Tom.
>
>
>
>   =



-- =

Dr. Bernhard Busch
Max-Planck-Institut f=FCr Biochemie
Rechenzentrum
Am Klopferspitz 18a
D-82152 Martinsried
Tel: +49(89)8578-2582
Fax: +49(89)8578-2479
Email bbusch@biochem.mpg.de



-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-03-09 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 12:42 NFS mount problem (2000 NFS filesystems) of linux clients to a solaris server Bernhard Busch
2007-03-08 13:08 ` Talpey, Thomas
2007-03-09 12:16   ` Bernhard Busch [this message]
2007-03-09 13:09     ` Talpey, Thomas
2007-03-09 14:46       ` Olaf Kirch
2007-03-09 15:04         ` Talpey, Thomas
2007-03-12 12:35           ` Talpey, Thomas
2007-03-12 16:57             ` Trond Myklebust
2007-03-09 14:25     ` Olaf Kirch
2007-03-13 13:11       ` Steve Dickson

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=45F15018.1060804@biochem.mpg.de \
    --to=bbusch@biochem.mpg.de \
    --cc=NFS@lists.sourceforge.net \
    --cc=Thomas.Talpey@netapp.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 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.