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 “Filesystem check procedure” under Diagnostic Procedures at the end of this document.

Reoccurrence of filesystem related error messages / mount problems after repair

If you have run a filesystem check until no errors were reported, or recreated a volume, this should permanently resolve the filesystem errors. If the errors return, the source of the problem remains. The most likely source is a hardware problem. A good first step is to replace the system board memory and the RAID controller, or failing that, the entire system. Once the source of the problem has been resolved, it will be necessary to proceed according to the “Filesystem check procedure” under Diagnostic Procedures at the end of this document.

Checkpoint database problems reported in system log Can’t delete checkpoints

The indication of a checkpoint database problem is either a hard error (e.g. cannot write) in the system log when attempting to delete a checkpoint, or an error message which specifically states “error in checkpoint database”. As the checkpoint filesystem is read-only, and treated as a separate filesystem in many ways, this problem must be addressed at the filesystem level. Specifically, via the chkpntabort command and a file system check.

It is generally recommended that this issue be escalated for assistance in accurately identifying the problem, and also to locate the source of the problem. The messages can vary considerably from the above; and similar checkpoint related messages could lead one down the wrong path toward applying an unnecessarily severe solution.

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. The diagnostic should be captured as close as possible to the time the messages occur, so that they may be seen in context in the system log. Also, collect as much information as possible about the circumstances surrounding the failure, e.g. when did the messages first appear, what was happening at the time, symptoms reported by users.

Typically in this case, it is necessary to abort checkpoints on the volume. This is done from the CLI. After verifying the diagnosis with engineering, access the CLI and enter “chkpntabort <volumename>”. StorEdge will prompt for confirmation. Answering “y”, “yes” to the prompt will result in the immediate deletion all checkpoints. A file system check is required as soon as possible after aborting

Chapter 2 NAS Head 2-73

Page 119
Image 119
Sun Microsystems 5310 NAS manual NAS Head

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.