Knowledge Base

Secondary menu

You are here

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.

A product serial number is required to create a Service Request. However, the Quantum DATASTOR Shield software does not have a serial number.

To create a Service Request for your Quantum DATASTOR Shield software, you will need the product serial number of the hardware with which you purchased the software: either the Quantum NDX-8d or the Quantum RDX® 8000.

Click the following links for information on how to find the product serial number for these units:

Vision: Database Folder Appears to Have Been Moved to an Unnamed Folder and a New Database Folder Created in Its Place (Bug 31772)

Problem:

On a Linux host (VisPerf.svt.quantum.com [IP 10.20.163.220]), the database folder appears to have been moved to an unnamed folder within /opt/quantum-vision, and a new database folder was created in its place.

Workaround:

1. From the CLI, enter service vision stop to stop the Vision services.2. Rename the new database folder (for example, to DB1).3. Rename the renamed original database folder (contains the rrd folder) back to database.4. From the CLI, enter service vision start to restart the Vision services.

Note:You can distinguish an SKM VM server serial number by the VM at the beginning of the serial number, for example, VM123456. The SKM appliance server does not contain the letters VM at the beginning of its serial number.

Labels SKM server serial numbers appear on a label in these locations:

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.

How to determine your media serial number

The serial number is usually located on the bottom or side of your media among one or more lines of alphanumeric characters. The table below shows examples of the one or more lines of alphanumeric characters on the bottom or side of various media types. The actual serial number is highlighted in red.

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.

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.