The StorNext 5 Compatibility Guide is available online at http://www.quantum.com/sn5docs. To open this guide, scroll down to the Compatibility Guides section and click on the StorNext 5 Compatibility link:

This article provides links to separate articles that describe how you can find the product serial number for the products that Quantum supports. This information is particularly useful to both customers and service engineers who need to find the product serial number to open a Service Request or begin to diagnose a problem.

The StorNext RAS message File System component [X] : License failed has 12 subtypes, based on the type of license failure. The ‘SR Notes’ section at the bottom of the RAS message describes the particular failure subtype. Please see the section below for explanations of each subtype.

You can find licensing information in the StorNext Licensing Guide, available either on the Quantum website or through the GUI by selecting Help > Documentation and selecting this guide.

You can view the current state of your licenses from the GUI, including capacity limits and expiration, by selecting Configuration > Licenses.

The Physical Media Changer tape drive [X] : Maintenance operation failure message refers to the automatic drive cleaning function in StorNext for a tape library. It has two possible causes, based on the details given under the ‘SR Notes’ section of the message.

When a drive requires cleaning, it returns a signal to StorNext. When StorNext receives that signal, a cleaning session is started, and it will not use that drive again to store or retrieve data until the cleaning session finishes. If a problem is encountered during this cleaning session, a RAS message is generated.

By default, Mac OS X treats all directories as if they have the Set-GID bit on. When a directory or a file is created, the group permissions will be set to the same value as the Parent and not the user default GUID.

The following steps provide DDM configuration for StorNext versions 5.2 and 5.2.0.1 which prevents one of the DDM licenses from being incorrectly used by the primary MDC.

Procedure

On both the primary and the secondary MDC, edit the /etc/hosts file and remove any aliases for the two MDCs. Ensure the IP address of the MDC is configured as the Fully Qualified Domain Name (FQDN) for both MDC. For example, here is a partial listing of a /etc/hosts file showing only the IP and the FQDN for the two MDCs:

When you are unable to mount a file system on some clients (when other clients can mount it fine), and unable to connect to the FSM process via a cvadmin tap, the user gets either a connection error or a license error.

Symptom:File system free space shows more space consumed than disk usage indicates in a StorNext File System. There are few, if any, sparse files.

Cause:On heavily used file systems, ones with many files added and deleted, the free space fragmentation can exceed 1,000,000 fragments. The current ABMFreeLimit calculation only returns the first 1,000,000 fragments back for reuse. The ABMFreeLimit parameter instructs the file system manager how to process the Allocation Bit Map, which in turn goes into the calculation of the file system free space.

StorNext: Truncation is not working

Files Are Not Truncated as Expected

Even if the truncation mintime requirement is met, files may not be truncated. Files are truncated only to keep the file system below the low-water mark (by default 75% of the capacity). When the daily truncation policies run, the oldest files are truncated first in an effort to bring the file system usage below the low-water mark. Thus, files may remain on disk even though their truncation mintime requirement has been met if the disk space is not required.

If a StorNext client is configured to access a StorNext metadata controller (MDC), but was previously configured to access an XSAN MDC, the following error message can occur frequently in the StorNext MDC system log:

StorNext File System: What Does the '[Node X] Disk Stripe Group 0 is DOWN' Message Mean?

Symptom:The following message displays on a metadata controller (MDC):fsm[13492]: [ID 550974 daemon.warning] StorNext File System FSS 'FSname[0]': [Node X] Disk Stripe Group 0 is DOWN for this client.

Cause:Stripe Group 0 must contain the metadata and usually includes the journal. While the MDC must be able to access this stripe group, the client is only required to have access to disks containing data.

Symptom:During Windows startup or a StorNext File System Service restart, an error dialog appears stating:

(Critical) StorNext File System FSS 'snfs1[0]': error: Unable to open C:\Program Files\StorNext\config\snfs1.cfg: No such file or directory

Cause:This is typically caused by the removal of a file system configuration file without removing its corresponding autostart entry in the StorNext File System Startup List. (The name of the problem file system is listed twice in the error message: one is in quotes and has a number in square brackets appended to it, and the other is the name of the config file listed, minus the '.cfg' suffix.)

StorNext: How to Change the Setting of the PERCENT_FULL_TO_MIGRATE Environment Variable

Issue:The PERCENT_FULL_TO_MIGRATE environment variable is the percentage value used to check against to determine if a medium is full enough to be migrated. Its default value is 99.9%. This article shows how to change this value.

Problem to AvoidBe careful when you perform an operating system update or reload!

To avoid accidentally reformatting all attached LUNs and removing all data on them, follow the advice given below. If these things happen and the updated system includes StorNext, this could keep StorNext from functioning.