Question

Locked

What is the maximum number of mounts on Microsoft Server for nfs

By isakson ·
I have windows unified data storage server (i.e,. win 2003 r2). I am exporting an nfs share to the Linux nodes. After about 15 or so clients mount the share, no more clients can mount it. Is there any way to increase the number of simultaneous mounts to the share?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

is the usage quota

by XnavyDK In reply to What is the maximum numbe ...

ramped down to 15? change it to unlimited.

Collapse -

Don't know how to find it

by isakson In reply to is the usage quota

I cannot find anything about usage quota for an nfs exported folder. Where would I look?

Collapse -

on the share

by XnavyDK In reply to Don't know how to find it

right click, properties, sharing quota/number of simultaneous users one box shows number of users, there should be a check box for unlimited. (memory leaks) the wording might be off I'm going from memory.

Collapse -

Not on the share

by isakson In reply to on the share

The share is published via nfs, not smb. There is nothing on properties for number of users. I suspect there is a registry setting somewhere in "Server for NFS" to increase the number of mounts available.

Collapse -

I think you have hit the maximum Read and Write to the Share..

NFS typically works with a "block" size of 8 K (though it may do fragments of smaller sizes). Since the maximum Ethernet packet is around 1500 bytes, the NFS "block" gets split into multiple Ethernet packets, even though it is still a single unit to the upper-level code, and must be received, assembled, and acknowledged as a unit. The high-performance workstations can pump out the packets which comprise the NFS unit one right after the other, just as close together as the standard allows. On the smaller, lower capacity cards, the later packets overrun the earlier packets of the same unit before they can be transferred to the host and the unit as a whole cannot be reconstructed or acknowledged. As a result, the workstation will time out and try again, but it will try again with the entire 8 K unit, and the process will be repeated, ad infinitum.

By keeping the unit size below the Ethernet packet size limitation, we ensure that any complete Ethernet packet received can be acknowledged individually, avoiding the deadlock situation.

Overruns may still occur when a high-performance workstations is slamming data out to a PC system, but with the better cards, such overruns are not guaranteed on NFS "units". When an overrun occurs, the units affected will be retransmitted, and there will be a fair chance that they will be received, assembled, and acknowledged.

Back to Networks Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums