Red Hat Bugzilla – Bug 300421
cannot mount 1000 folder in storm on LAN
Last modified: 2007-11-30 17:07:48 EST
Description of problem:
When mounting more then 500 mount-point then mount ends.
Version-Release number of selected component (if applicable):
nfs-utils-1.0.9-23, util-linux-2.13-0.45, kernel2.6.18-8.1.8.el5
Steps to Reproduce:
Server share some directory,
0. [root@server] cat /etc/exports
1.[root@client]# cat script1
for i in `seq 1 1020`
[ ! -d /mount3/$i ] && mkdir -p /mount3/$i
$MOUNT -o tcp server:/mount2/$i /mount3/$i || exit 1
ls -d /mount3/$i;
mount: vepro:/mount2/508 failed, reason given by server: Permission denied
When I am trying to "mount" in storm in LAN and the number exceed +-500 than
there is no free ports, because it's fast like 30 seconds and ports are in state
"TIME_WAIT" ... "netstat -an | grep 2049".
Some customer wants to mount all mount-point because of some mailing list, see
mounting in storm, mount could wait for ports which are in TIME_WAIT state.
Now you can mount many folders in storm like that:
If you change "type of port" to "insecure" on server side .
# there is more free ports like 1024 to 61000.
Or you make some changes to files in "/proc/sys/net/ipv4/*" on client side,
for ex "echo 8 > /proc/sys/net/ipv4/tcp_max_tw_buckets" -- faster ports unlocking.
Do you get better results if you don't use '-o tcp' here? That option makes it
so that mount.nfs uses TCP sockets for everything and can prematurely make you
run out of reserved ports in userspace. If you don't use that you'll still get
TCP mounts by default, but the communication with mountd and the portmapper is
done with UDP.
All 1020 mount-points are mounted without "-o tcp"
So can we close this as not a bug?
Ok close it.