Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1011355.1
Update Date:2010-01-13

Solution Type  Troubleshooting Sure

Solution  1011355.1 :   Sun StorageTek[TM] 5000 Series NAS: Troubleshooting Performance Issues  

Related Items
  • Sun Storage 5210 NAS Appliance
  • Sun Storage 5220 NAS Appliance
  • Sun Storage 5310 NAS Appliance
  • Sun Storage 5320 NAS Gateway/Cluster System
  • Sun Storage 5320 NAS Appliance
  • Sun Storage 5310 NAS Gateway System
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Network Attached Storage


  • NAS 5000 poor performance
  • file copy is slow
  • access is slow

This document defines a step-by-step procedure for troubleshooting performance issues on the NAS. It is primarily focused on file copy performance to and from NFS and CIFS clients, though many of the recommendations will be useful for other issues. The document links to several Technical Instructions with the individual procedures for each step.

This issue will normally be reported as "file copy is slow", "performance is poor" or "access is slow". In severe cases, it may also be reported that the system or data service has hung.

Steps to Follow
Please follow each troubleshooting step below. The steps will provide instructions or a link to a document to collect data, validate the data and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Step 1 - Verify speed and duplex settings at both the NAS and the network switch. Also, note that network clients have the same requirements, and may also be the source of the problem <Document: 1011070.1>

Step 2 - Verify network settings and check for network errors. Misconfiguration and network errors are a common cause of poor performance
< Document: 1008489.1 >

Step 3 - Ensure Operating system and storage firmware are updated to current revisions. Please contact Sun Support Services if you cannot access any content returned by this search. There have been a number of performance-related enhancements as we develop new ways to improve the product. Both OS and backend firmware are included in the software update links. Follow the instructions and apply all updates.

Step 4 - Verify that volume and LUN layout is optimally configured. Well-planned initial configuration of LUNs and volumes can improve performance significantly. For NFS clients, verify read and write blocksize. We recommend setting NFS clients to use a 32K blocksize for both reads and writes. This is normally done by adding rsize=32768, wsize=32768 to the mount options <Document: 1004361.1>

Step 5 - Verify that sufficient free space is available and check files per directory. Each volume must have some free space for file operations and internal databases. A very large number of files in a single shared directory can also negatively affect performance
< Document: 1012873.1 >

Step 6 - Verify disk space used for Checkpoints. Checkpoints, if not properly managed can take a large amount of disk space and slow the entire system < Document: 1004363.1 >

Step 7 - Confirm that cache is enabled and LUN are optimal. A problem in either of these areas will cause extreme performance degradation until corrected < Document: 1011368.1 >

Step 8 - Check background processes and CPU utilization. Other system and user processes may be consuming CPU cycles and other system resources. Also, keep in mind that initializing new LUNs or performing other storage maintenance operations may have a negative effect on disk performance < Document: 1017984.1 >

Step 9 - Collect the NAS extractor, diagnostic and backend performance statistics to prepare for a support case or escalation. The diagnostic collection should be done while the performance problem is present
<Document: 1005474.1>

Step 10 - Collect support data from the storage. If the issue is storage-based, this will help the Engineer to resolve the issue. Note that this procedure will not work for Gateway configurations. In this case, collect the data directly from the backend storage using the provided management tools < Document: 1002481.1 >

Step 11 - Collect a network trace. Follow the instructions to set up a trace, set the filter to capture only traffic between the NAS and the workstation performing the file copy or other problematic operation. Start the trace, create the problem, then stop the trace
< Document: 1004130.1 >

Step 12 - At this point, if you not been able to resolve the issue with the troubleshooting steps above, further troubleshooting is required. Contact Sun Support and be prepared to provide the data collected in the above steps.

Sun StorageTek 5320 NAS Gateway/Cluster System
Sun StorageTek 5320 NAS Appliance
Sun StorageTek 5320
Sun StorageTek 5310 NAS Gateway/Cluster System
Sun StorageTek 5310 NAS Gateway System
Sun StorageTek 5310 NAS Appliance
Sun StorageTek 5220 NAS Appliance
Sun StorageTek 5210 NAS Appliance

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

[email protected]

The Knowledge Work Queue for this article is KNO-STO-NAS.


NAS, normalized, CIFS, NFS, performance, slow, file copy, access
Previously Published As

Change History
Date: 2010-01-13
User Name: Will Harper
Action: Currency check
Comment: Checked all links, all current
Date: 2007-10-03
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok (normalized)
Checked status of dependent articles

This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.