| Sun StorageTek 5800 System Release Notes |     |
| Sun StorageTek 5800 System Release Notes | |
|
Sun StorageTek 5800 System Release Notes |
This document contains important information about the Sun StorageTek 5800 system that was not available at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the Sun StorageTek 5800 System.
The Sun StorageTek 5800 system is an online storage appliance featuring a fully integrated hardware and software architecture in which the disk-based storage nodes are arranged in a symmetric cluster. The clustered and redundant design provides high availability, good performance, and exceptional data integrity.
The Sun StorageTek 5800 system provides the following features:
This section provides an approved platform list for the Sun StorageTek 5800 system Application Programming Interfaces (APIs) including:
This section provide information about functional limitations and bugs filed against this version 1.0 product release. Note that if a recommended workaround is available for a bug, it follows the bug description.
The section contains the following topics:
Note that if a recommended workaround is available for a bug, it follows the bug description.
The functional limitations of the version 1.0 release are as follows:
This section describes known issues and bugs related to installing and initially configuring the Sun StorageTek 5800 system.
Bug 6403228 - When you attempt to bring up a server node with missing or faulty disks, that server node might fail during the startup procedure. Contact Sun Support to schedule replacement of the failed drives.
Bug 6405531 - You can use netcfg and ifconfig to change the cluster administrative and data virtual IP addresses (VIPs). However, you cannot change the service node's IP address. Thus, if you have a conflict with the predefined factory service node IP, you will be unable to change it. Contact your Sun service representative for assistance.
This section describes known issues and bugs related to using the command line interface (CLI).
Bug 6247537 - After a master failover occurs, the following message may appear on the console when you log in to the CLI:
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed...
This message is innocuous and can be ignored.
Bug 6327227 - If disabling a disk fails (for example, because the disk cannot be unmounted), no warning message is displayed. Use hwstat -v to view the status of the disk.
Bug 6380366 - If you access the CLI and type the mdconfig command before the database is ready, the following error message is displayed:
Timed out waiting for the state machine
Workaround - Ensure that the database is operational by entering sysstat before using the mdconfig command.
Bug 6405506 - If you configure an SMTP server and a port in the CLI using the netcfg command, the switch will not recognize the port you configured.
Bug 6406170 - When you make a configuration change, certain properties require a reboot to take effect. Once the change is entered, however, you can no longer determine the current value since the netcfg command shows the new (pending) value instead. You also cannot tell that the displayed value is a pending value and that a reboot is still required.
Bug 6241900 - If you log in to the system, enter the CLI help command, and then enter additional commands, such as version and sysstat, an immediate exit from the login session results. No error message is displayed.
Bug 6403938 - Should you inadvertently add the -v or --verbose option to certain CLI commands, such as hwcfg, where its use is not supported, the following error appears:
unknown error: Can't find resource for bundle java.util.PropertyResourceBundle, key common.version.name
Bug 6408010 - Should you use the wipe command, a NullPointerException appears on the console. The operation will continue despite the appearance of this error.
Bug 6409249 - Entering the commands hwstat, hwstat -v, and sysstat -v shows the disk status as disabled and not as initializing while the disk is being enabled. This is confusing and can lead to a duplicate enable operation being performed.
Bug 6411146 - If you attempt to commit an invalid schema.xml file with the mdconfig -c command, the CLI becomes non-operational and eventually times out.
Bug 6421305 - Note the following with the df command:
You can use df effectively to view raw storage statistics for each disk in the cluster. Therefore, used is not equivalent to the total number of Object bytes stored in the system. For example, it includes space consumed by data parity, Object headers and footers, query indexes and so on.
Storage utilization statistics reflected by df are refreshed every three minutes.
When using df to view storage utilization, be aware that the system reserves 15% of raw storage. This space is available so data recovery can be completed should a node or disk fail on a full cluster.
Bug 6421293 - If you power up the system, access the CLI, and then enter sysstat, a Data Integrity Verified indication appears. At this point, however, the Data Doctor tool has not completed a lost fragment recovery cycle and is unable to determine whether or not all data fragments are indeed accounted for.
Bug 6421314 - If you enter the sysstat command and its --verbose option, the system output that appears does not include node identifiers.
Bug 6427699 - If you attempt to update the schema using mdconfig while a system load is occurring, the result is that the database becomes suspended in a create schema state.
This section describes known issues and bugs related to using the client API.
Bug 6395771 - Harmless errors are printed to stdout during query operations with a select clause. For a cluster, they are displayed in the log. For the emulator, these errors are written to the shell where the emulator is launched.
Bug 6403951 - The emulator supports the Delete Metadata operation of NameValueObjectArchive.delete and hc_delete_ez. However, the emulator does not remove the underlying data file when the last metadata record is deleted. The semantics are correct, but the underlying space is not reclaimed.
Bug 6407770 - If you try to install the Software Development Kit (SDK), the emulator configuration script fails if the specified directory name contains spaces.
Bug 6427145 - When using the C API, the overall metadata size of a stored data item is limited to 76384 bytes. (The exact maximum size depends on many factors and should not be relied on). This limitation does not apply to data stored using the Java API.
Bug 6427141 - The behavior of metadata values that contain non-printable characters is not guaranteed. In particular, two known limitations are that metadata values cannot contain the null character, and that metadata values that contain the <LF> character will have the <LF> values silently removed in the stored value.
This section describes general issues related to the Sun StorageTek 5800 system.
Bug 6187582 - Deleting an object twice produces the following error message:
ERROR: failed to retrieve object: request failed with status 400: no oa ctx.
ERROR: failed to retrieve object: request failed with status 400: noSuchObject
Bug 6194366 - The supported metadata type field, double, does not work in views in the version 1.0 release.
Bug 6268321 - If the client connection is lost during store and delete operations, the following error is displayed:
INFO: request failed with IOException...
Error in parsing the status line from the response: unable to find line starting with "HTTP"
Workaround - The store failed because of a network problem. Retry the operation.
Bug 6187879 - Store operations become suspended and then time out in the client. If you then try the operation again, you might store the same data twice.
Workaround - Delete the second instance of the stored object.
Bug 6291970 - Known issues arise when you perform concurrent delete operations.
Workaround - Until this issue is resolved, perform delete operations from a single client connection at a time.
Bugs 6355668 and 6403926 - Initial input/output (I/O) operations on an otherwise idle cluster may be slower than usual.
Bug 6398940 - With the exception of the mail header itself, email alerts do not provide cluster-specific information to enable you to distinguish between systems.
Workaround - Read the mail headers to determine where the alert originated. It will be the Administrative VIP configured for the cluster.
Bug 6402543 - When moving a rack, there is no way to power all the components down, since the CLI shutdown command powers down only the nodes.
Bug 6392770 - Starting up or shutting down the cluster without all nodes being online may force the query indexes to be rebuilt. Until the rebuilding process is finished, query results may be incomplete. See the sysstat command for the status of the query engine.
Bug 6408658 - If you attempt to determine when a file or directory was last modified or created, be aware that there are inconsistencies in date reporting. For example, the directory listing getlastmodified might show a significant offset from Coordinated Universal Time (UTC), while the creationdate is about the same without the offset. These times should be similar or very close.
Bug 6413587 - When the Sun StorageTek 5800 node BIOS is booting up, the following two conditions may occur:
Workaround - Power on the node again through the front panel power switch. If this does not fix the problem, remove the power cord, wait 30 seconds, and then connect the power cord once more.
Bug 6402478 - Despite the fact that a proper failover alert was not sent, the following alert appears indicating that you should perform a cluster assessment:
Cluster is booting or master failed over
Other than by visually inspecting the cluster, there is no way to determine if the switch has failed over.
Bug 6422741 - If you use a good disk from another node during a disk replacement, it causes the node to assume the identity of the previous disk owner.
Workaround - Use only new disks when performing a disk replacement.
Bug 6424800 - With disk write cache enabled, there is a very small probability that a complete power outage or three simultaneous catastrophic disk failures can result in data loss for recently stored files. Testing of the failure scenarios presented here has not yet resulted in any data loss.
Bug 6425530 - If your primary switch is not functioning and you are operating on the secondary switch, rebooting a node repeatedly fails to bring up the data VIP at start-up. In addition, the system configures some unusual interfaces, eventually escalates, and then reboots once more. Rebooting the entire cluster while running on the secondary switch causes the cluster to become non-operational.
Bug 6423238 - In some instances, five disk failures will cause the query engine to become disabled.
Workaround - Reboot the cluster and the query engine will automatically repair itself in approximately 12 hours.
|
Sun StorageTek 5800 System Regulatory and Safety Compliance Manual |
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
| Sun StorageTek 5800 System Release Notes | 819-3813-10 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
library