RAID configuration changed. If syslogd logging was enabled, these results should be included as well. Find out whether remote access is available to the site, and if appropriate, provide the necessary details to accomplish this.

After reviewing the case, engineering may make specific recommendations and modifications, or they may recommend that you proceed with the filesystem repair. For instructions on how to complete a filesystem repair, see the heading “Filesystem check procedure” under Diagnostic Procedures at the end of this document.

File system related error messages

The following are examples of messages that indicate a problem with the filesystem:

Broken directory, run check

Corrupted/run check

Cleaner error

These messages are generated when unsuccessful attempts are made to access particular files or directories. The message may occur only when accessing a particular directory; or it may fill the system log entirely. You can get a general idea of the degree of the problem by the frequency of the error messages.

This problem manifests as an inability to access particular files and folders, which often causes a hang condition or a timeout.

The message “run check” refers to the filesystem check, or “fsck”. The filesystem check is a time consuming process, which is potentially destructive to data. Generally speaking, unless you have a very good idea about the source of the problem, the issue should be escalated. It is almost a certainty that a filesystem check will be needed in this case. However, it is important to work toward locating the source of the problem to ensure that it will not recur.

A diagnostic email, with all attachments, is required to escalate this type of issue. The primary source of information for this case is the system log. Also, collect as much information as possible about the circumstances surrounding the failure, e.g. did the system lose power, what symptoms were seen by the clients, was any hardware or RAID configuration changed. These particular log messages always correspond to an attempt to access a particular directory or file, this may provide a clue to the source of the problem.

If syslogd logging was enabled, these results should be included as well. Find out whether remote access is available to the site, and if appropriate, provide the necessary details to accomplish this.

2-72Sun StorEdge 5310 NAS Troubleshooting Guide • December 2004

Page 117 Page 119
Page 118
Image 118
Sun Microsystems 5310 NAS manual File system related error messages
Page 117 Page 119

5310 NAS specifications

Sun Microsystems, known for its innovative computing solutions, launched the Sun 5310 Network Attached Storage (NAS) system, which marked a significant advancement in the realm of storage solutions in the early 2000s. The 5310 NAS was designed to provide high-performance, reliable, and scalable storage tailored for enterprise environments.

One of the standout features of the Sun 5310 NAS is its file-serving capabilities, which support multiple protocols, notably NFS (Network File System) and CIFS (Common Internet File System). This dual-protocol support allowed organizations to seamlessly integrate the NAS into diverse IT ecosystems, facilitating interoperability between UNIX, Linux, and Windows systems. The enhanced file-sharing capabilities made it an ideal solution for businesses with mixed operating environments.

The Sun 5310 NAS incorporates cutting-edge technologies to ensure high availability and data integrity. The system utilized a RAID (Redundant Array of Independent Disks) technology, providing various RAID levels to protect against data loss while optimizing performance. Additionally, the device featured hot-swappable drives, enabling maintenance and upgrades with minimal downtime, a crucial factor for business continuity.

Equipped with advanced management software, the Sun 5310 NAS offered users an intuitive interface for monitoring storage health and performance. This software included comprehensive reporting functionalities that allowed IT administrators to oversee usage patterns and capacity planning efficiently.

Scalability was another defining characteristic of the Sun 5310 NAS. The system could easily expand with additional storage modules, accommodating the growing needs of an organization without the necessity for complete system overhauls. This flexibility ensured that businesses could adapt their storage solutions to meet evolving data storage needs without incurring significant costs or disruptions.

In terms of performance, the Sun 5310 NAS featured high I/O throughput achieved through its robust hardware architecture and optimized file serving capabilities. This performance baseline was crucial for organizations that relied on heavy data workloads and required rapid access to information.

In summary, the Sun 5310 NAS from Sun Microsystems embodied a forward-thinking approach to network storage, blending reliability, scalability, and multi-protocol support. Its user-friendly management software, combined with the robustness of RAID technology and hot-swappable drives, made it a preferred choice for enterprises looking to streamline their storage infrastructure while safeguarding critical data.
Top Page Image Contents