![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Configuración del servidor NFS en Solaris
Problemas en NFS http://www.groupsrv.com/linux/ptopic18779.html Depending on the number of LINUX clients, you may need to increase the thread count on the Solaris NFS server. I have seen this type of problem before at client sites where the default NFSD count was used. The default is 1, which is VERY low. You can set these by (from www.sun.com) Solaris 8 and prior server threads that can run at nce. For Solaris 9 and subsequent releases parameter NFSD_SERVERS in the /etc/default/nfs file.Those threads are created and destroyed dynamically. They each consume 16K of kernel stack and most likely handle one NFS filesystem block. They also run at a higher priority than the timeshare class. Since the memory requirement is cheap and dynamic, there are no big drawbacks to setting this value much higher on an NFS server (a conservative nfsd thread value = num_of_cpus128). For Solaris 8, edit /etc/init.d/nfs.server : /usr/lib/nfs/nfsd -a 1024 For Solaris 9, edit /etc/default/nfs: NFSD_SERVERS=1024 Then kill and restart the daemon /etc/init.d/nfs.server stop /etc/init.d/nfs.server start Notes : NFS server threads run at a high priority. With a really high number of threads they may potentially starve other non-NFS related work. In this case, Solaris 9 - Solaris Resource Manager (SRM) may be used to limit the CPU time allotted to NFS. Tim Sesow tsesow@nsllc.com Link to this Page
|