PowerScale OneFS

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

This article is no longer maintained.

In OneFS 9.10, S3 PUT requests that include the x-amz-trailer header are rejected with an HTTP 501 (NotImplemented) error. In earlier releases, including OneFS 9.7, the same requests are accepted without error. This represents a behavioral change in S3 request validation.

Describes System Pool mode behavior in OneFS 9.15+ and explains the associated alerts to help interpret cluster state and identify potential issues.

This article explains why one cluster in a syncIQ relationship (source or target) may report more used disk space than the other cluster. Both clusters should display identically used disk space. SyncIQ jobs are up to date.

Nodes run out of memory due to lockdata not releasing used memory.

Nodes may panic with FAILED ASSERTION when fail to decode quota or snapshot attributes from extension blocks after upgrading to OneFS 9.2.0.0 or 9.2.1.0.

After upgrading OneFS to 9.5.1.5, 9.7.1.10, 9.10.1.3 or 9.12+, users may not be assigned the correct GID from a non-AD provider.

How to preserve specific files or directories during an upgrade of OneFS.

A faulty Dual inline memory module (DIMM) in a node may cause backend latency.

It is possible for the same username to exist across multiple authority providers, either local to OneFS or external. This can result in an inability to log in for the given user. A second root user on another provider can make it appear that root access to the cluster is unavailable.

This article describes a known issue with ConnectX-6 (CX6) InfiniBand backend path failover. An architectural change introduced in CX6 InfiniBand Host Channel Adapter (HCA)s affects backend path redundancy, resulting in unexpected failover behavior.

NFSv4.1 and v4.2 are enabled automatically during the upgrade process when upgrading to certain versions of OneFS.

A Gen6 DE peer node pair (H400, A200, A2000) can sometimes start generating error messages indicating problems with their NTB link. Errors can include repeated 'NTB link up/down' messages, and link speed negotiation errors.

Dell PowerScale OneFS remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

Explore the Dell End of Service Life (EOSL) and End of Life (EOL) list for converged infrastructure, storage, and storage networking products. Access End-of-Life documents for hardware, software, and firmware release and service dates

How to place the PowerScale OneFS cluster into Maintenance Mode to avoid receiving alerts or triggering Dial-Home service requests (SR) during a maintenance activity.

How to identify duplicate Service Principal Names (SPNs) in Active Directory (AD), which can cause Kerberos authentication to fail.

Due to an internal change in the EN06 and newer, and 0006 and newer firmware for Seagate Megalodon drives, any drives upgraded non-disruptively to this firmware may go into smartfail unnecessarily when a drive is replaced if the node has not yet been rebooted since the upgrade. This issue affects OneFS versions 8.0.0.4 and older, 8.0.1.0 and 8.0.1.1.

Clusters are reporting AD server missing needed Service Principle Names (SPNs) after a Superna Failover/Failback for SPNs that do not match any cluster SmartConnect Zone Name (SCZN).

Upon upgrading PowerScale OneFS, sudo commands ask for a password three times and then fails to run the command.

When there are hard links in the path covered by a SyncIQ policy, the initial sync of that policy can fail at the target cluster with an error indicating a file was already stubbed. (CBM_ALREADY_STUBBED)

Modify SNMP channel via WebUI reset use-snmp-trap flag on Isilon OneFS 8.0: CELOGv2

This article explains how to modify cluster and windows server/client configurations to enable and/or require Security Signatures.

Firmware package installation would not be complete.

This article describes how to use the AutoBalanceLin job to quickly free space if a single node pool is full or almost at 100% capacity. This procedure should only be used if all other methods of freeing disk space on a node pool have been exhausted.

How to resolve dial-home tests failing after a first successful attempt.

How to properly delete snapshots from a cluster.

This article is useful to troubleshoot Application Programming Interface (API) issues against the cluster directly using curl commands. Use it to rule out issues with custom scripts or application code.

This shows how to choose between displaying available space as cluster size or quota hard threshold.