Always Disable “Over Commit” Before Creating LUNs When Using StorNext with Q-Tier

Why Disable "Over Commit" When Using StorNext and Q-Tier?

When you use StorNext with Quantum’s QXS Q-Tier, always disable the “over commit” feature before you create any LUNs. If “over commit” is enabled, it is possible to overprovision the LUNs and unknowingly run out of disk space. This could result in the loss of files that were written into the LBA range that was not provisioned with physical storage. This article provides some guidelines and recommendations.

Notes on Q-Tier Capacity Allocation and Utilization

Q-Tier determines used capacity based on used pages in the virtual LUN, and it determines which pages are used based on which pages are allocated. Pages are allocated when being written to by StorNext.

RAS Message – StorNext Storage Manager Component : Configuration not supported

The StorNext Storage Manager component : Configuration not supported message is a RAS Event (called a Service Ticket in the StorNext GUI). This message is generated by the StorNext daily health check, which usually runs at 7:00 a.m. It may also arrive by e-mail, if e-mail notification is configured in the GUI.

When sent by e-mail, the message will look similar to this:

StorNext RAS Message - File System component [X] : License failed

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.

StorNext RAS Message - Physical Media Changer tape drive [X] : Maintenance operation failure

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.

SR Notes Section: No Cleaning Media Available

StorNext RAS Message – File System Component [x] Not Responding

The message that a StorNext filesystem is not responding has two forms, which can be distinguished by the “SR Notes” section in the body of the message.

Form 1: <Reporting System> : fs <”file system name”> on host <FSS host system> not currently accessible (possibly stopped administratively). Thread <thread ID>pid 0, still trying.  Ticket creation time: <date & time>

Form 2: <Reporting System> : fs <”file system name”> : Timeout while attempting to force data flush for file <”filename”> (inode <inode number>) for file system <”file system name”> on host <Problem system>. See cvlog for more details.  Ticket creation time: <date & time>

StorNext GUI: Installing a SSL Certificate from a Certificate Authority

Introduction to SSL

SSL, or Secure Socket Layer, is a technology which allows web browsers and web servers to communicate over a secured connection. This means that the data being sent is encrypted by one side, transmitted, then decrypted by the other side before processing. This is a two-way process, meaning that both the server AND the browser encrypt all traffic before sending out data.

StorNext File Systems - Linked Files & Directories and Their Effect

StorNext File Systems - Linked Files & Directories and Their Effect

For a general discussion of hard links, soft links, Windows shortcuts, and Windows junction files, refer to the Wikipedia articles
“mklink” in Windows Vista, Windows 7, Windows 2008, and beyond

StorNext File System: Unable to Mount File System or Connect to FSM Via cvadmin

StorNext File System: Unable to Mount File System or Connect to FSM Via cvadmin


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.

One or more of the following errors might be observed:

FSM may have too many connections active.

[1214 11:27:31] 0xb7e2f6b0 (**Error**) Maximum number of connections (n) exceeded.
Connection by <hostname> rejected.

StorNext: File System Free Space Shows More Space Consumed Than Disk Usage Indicates

StorNext: File System Free Space Shows More Space Consumed Than Disk Usage Indicates ("du" and "df" Outputs Differ)

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

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: Resolving Authentication Error Messages on the MDC after Connecting a StorNext Client That Was Previously an XSAN MDC Client


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:

NSS received unexpected authenticated message from <StorNext Client IP address>. DISCARDED.

StorNext: Resolving when a StorNext File System Client Fails to Mount a StorNext File System

StorNext: Resolving When a StorNext File System Client Fails to Mount a StorNext File System

On a StorNext or StorNext FX system, you receive the following error:

mount.cvfs: Can't mount filesystem 'FILESYSTEMNAME'.
Check system log for details. Invalid argument

The system cannot resolve the IP address or hostname defined in the fsnameservers file.

Use this procedure to troubleshoot this problem.

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

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

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.

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.

StorNext: Error in Windows - Unable to Open Configuration File: No Such File or Directory

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

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

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

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.

StorNext: How to Avoid Reformating All Connected LUNs and Losing Data When the OS Is Updated or Reloaded

Problem to Avoid
Be 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.

StorNext: Truncation is not working

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.