Quick question - what's the data link protocol (Ethernet, IB, etc.) and link rate that you're using?
On Tue, Sep 04, 2018 at 02:05:33PM -0400, Zoltan Forray wrote: > We are still fighting issues with ISILON storage. Our current issue is with > NFS timeouts for the storage a server is using. We see message like these > in the server /var/log > > Sep 4 13:21:49 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:21:49 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:21:49 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:21:49 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:22:14 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:22:15 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu > not responding, still trying > Sep 4 13:22:16 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu OK > Sep 4 13:22:16 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu OK > Sep 4 13:22:16 earth kernel: nfs: server hhisilonnfs23.rams.adp.vcu.edu OK > > OS folks say the NFS mount is setup as IBM recommends in various documents. > So they asked us to implement the nfstimeout option from this document ( > https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.0/com.ibm.itsm.client.doc/r_opt_nfstimeout.html). > Yes I realize it is primarily for a client backup of an NFS mount, but the > statement: > > Supported Clients This option is for all UNIX and Linux clients. *The > server can also define this option*. > > throws us - kind-of implying I can use this from the server perspective? > But I can't find any documentation to support using it from the server. > > For you Linux guru's - this is what the mount says: > > hhisilonnfs23.rams.adp.vcu.edu:/ifs/NFS/TSM on /tsmnfs type nfs > (rw,relatime,sync,vers=3,rsize=131072,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.19.12,mountvers=3,mountport=300,mountproto=udp,local_lock=none,addr=192.168.19.12) > > Any thoughts? Suggestion? Are we simply expecting too much from NFS? > > My OS person also asks why ISP is so slow to write to NFS? When they did a > test copy of a large file to the NFS mount, they were getting upwards of 8G/s > vs 1.5-3G/s when TSM/ISP writes to it (via EMC monitoring tools). > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://phishing.vcu.edu/ -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
