Home > Storage > PowerScale (Isilon) > Product Documentation > Storage (general) > PowerScale OneFS Large File Support > Configuring large file support
Step 1: Verify OneFS version
The uname CLI command output displays a cluster’s current OneFS version.
For example:
# uname -sr
Isilon OneFS v9.0.0.0
The current OneFS version information is also displayed at the upper right of any of the OneFS WebUI pages.
Step 2: Upgrade cluster’s OneFS version, if required
If the output from step 1 shows the cluster running a release earlier than OneFS 8.2.2, an upgrade is required. The upgrade can be accomplished either through the isi upgrade cluster CLI command or in the OneFS WebUI at Cluster Management > upgrade.
Once the upgrade has completed it must be committed, either by following the WebUI prompts, or through the isi upgrade cluster commit CLI command.
Step 3. Verify cluster’s large file support configuration
Run the isi_large_file -l CLI command to see a cluster’s large file support status. The following output example shows that the cluster already has large file support enabled:
# isi_large_file -l
System version: v9.2.0.0
Large file support ready: Yes
Large file support enabled: Yes
Current maximum file size: 16TB
Achievable maximum file size: 16TB
Conversely, the following example shows a cluster that does not have large file support enabled:
# isi_large_file -l
System version: v9.2.0.0
Large file support ready: Yes
Large file support enabled: No
Current maximum file size: 4.0TB
Achievable maximum file size: 16TB
Step 4. Confirm large file support compliance
To ensure that all node pools in the source cluster and any target clusters are compliant, run the following command:
# isi_large_file -c
The following table provides a description of the fields in the isi_large_file -c command output:
Field | Description |
Disk Pool Name | Node pool name and this disk pool ID. |
Members | Current nodes and drives that are part of this disk pool. |
Usable | Current usable capacity of this disk pool. |
Required | Usable capacity required for this disk pool to support large files. |
Potential | The maximum usable capacity that this disk pool could support at the ideal neighborhood size (10 nodes for Isilon Gen6 platform, 20 nodes for PowerScale and earlier-generation Isilon hardware). Be aware that, as a cluster grows, disk pools might shrink in size to contain ideal neighborhood size members. |
Capable | Whether this disk pool has the disk size and number per node to support large files. |
Add Nodes | If this disk pool is capable, how many more nodes need to be added. |
Step 5: Resolve any compatibility check issues
If a cluster configuration does not meet the minimum criteria for large file support, the compatibility checking command output will indicate what the issue is and, where appropriate, what corrective action can be taken for a resolution. For example, consider the following output from a four-node Isilon A2000 cluster:
# isi_large_file -c
Checking cluster compatibility with large file support...
NOTE:
Isilon requires ALL clusters in your data-center that are part of
any SyncIQ relationship to be running on versions of OneFS compatible with large file support before any of them can enable it. If any cluster requires upgrade to a compatible version, all SyncIQ policies in a SyncIQ relationship with the upgraded cluster will need to resync before you can successfully enable large file support.
* Checking SyncIQ compatibility...
- SyncIQ compatibility check passed
* Checking cluster disk space compatibility...
- The following disk pools do not have enough usable storage capacity to support large files:
Disk Pool Name Members Usable Required Potential Capable Add Nodes
-----------------------------------------------------------------------------------------------------------
a2000_200tb_800gb-ssd_16gb:2 1-4:bay3,7,11,15,19 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:3 1-4:bay4,8,12,16,20 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:4 1-4:bay5,9,13,17,21 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:5 1-4:bay6,10,14,18,22 175TB 213TB 439T Y 1
Disk Pool Name - Node pool name and this disk pool id
Members - Current nodes and bays in this disk pool
Usable - Current usable capacity of this disk pool
Required - Usable capacity required for this disk pool to support large files
Potential - The max usable capacity this disk pool could support at the target node count
Capable - Whether this disk pool has the size of disk and number per node to support large files
Add Nodes - If this disk pool is capable, how many more nodes need to be added
The cluster is not compatible with large file support:
- Incompatible disk pool(s)
a2000-1# isi_large_file -c
Checking cluster compatibility with large file support...
NOTE:
Isilon requires ALL clusters in your data-center that are part of
any SyncIQ relationship to be running on versions of OneFS compatible
with large file support before any of them can enable it. If any
cluster requires upgrade to a compatible version, all SyncIQ policies
in a SyncIQ relationship with the upgraded cluster will need to resync
before you can successfully enable large file support.
* Checking SyncIQ compatibility...
- SyncIQ compatibility check passed
* Checking cluster disk space compatibility...
- The following disk pools do not have enough usable storage capacity to support large files:
Disk Pool Name Members Usable Required Potential Capable Add Nodes
-----------------------------------------------------------------------------------------------------------
a2000_200tb_800gb-ssd_16gb:2 1-4:bay3,7,11,15,19 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:3 1-4:bay4,8,12,16,20 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:4 1-4:bay5,9,13,17,21 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:5 1-4:bay6,10,14,18,22 175TB 213TB 439T Y 1
Disk Pool Name - Node pool name and this disk pool id
Members - Current nodes and bays in this disk pool
Usable - Current usable capacity of this disk pool
Required - Usable capacity required for this disk pool to support large files
Potential - The max usable capacity this disk pool could support at the target node count
Capable - Whether this disk pool has the size of disk and number per node to support large files
Add Nodes - If this disk pool is capable, how many more nodes need to be added
The cluster is not compatible with large file support:
- Incompatible disk pool(s)
The most pertinent line of the output is last one, which states the fact that the cluster in its current configuration is unsuitable for supporting files larger than 4 TiB.
The summarized results of the two suitability checks are at the top of the output. In this case, the SyncIQ check passes, indicating that there are no uncompliant replication partner dependences. The second check of this cluster’s disk space (usable capacity) reports a failure. Beyond these checks, the following section of the output contains the bulk of the detail:
Disk Pool Name Members Usable Required Potential Capable Add Nodes
--------------------------------------------------------------------------------------------------
a2000_200tb_800gb-ssd_16gb:2 1-4:bay3,7,11,15,19 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:3 1-4:bay4,8,12,16,20 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:4 1-4:bay5,9,13,17,21 175TB 213TB 439T Y 1
a2000_200tb_800gb-ssd_16gb:5 1-4:bay6,10,14,18,22 175TB 213TB 439T Y 1
The following table displays this information about the first disk pool more clearly, with a description for each item:
Item | Result | Description |
Disk Pool Name | a2000_200tb_800gb-ssd_16gb:2 | Node pool name and this disk pool ID (2 in this case) |
Members | 1-4:bay3,7,11,15,19 | Current nodes and drives in this disk pool |
Usable | 175TB | Current size (usable capacity) of this disk pool |
Required | 213TB | The disk pool size (usable capacity) required to support large files |
Potential | 439T | The largest this disk pool could be at the ideal neighborhood size (20 for PowerScale, 10 for Isilon Gen6, 30 for Isilon Gen5) |
Capable | Y | Whether this disk pool could support large files |
Add Nodes | 1 | If this disk pool is capable of supporting large files, how many more nodes are required to support large files |
For this Isilon A2000 cluster configuration, in each of the four disk pools, the delta between Usable and Required shows that each pool misses the minimum capacity requirement for large file support by 52 TiB. However, the Capable field indicates that this A2000 has the potential to be a viable configuration with the corrective action recommend in the Add Notes field. So, in this case, the addition of a second A2000 chassis (four nodes total, with one node per disk pool) to the cluster would meet the requirements for large file support.
Step 6: Configure large file support
Once you clear a stand-alone cluster, or all the clusters with replication dependencies, by running the compatibility checking script, enable large file support by running the following CLI command, which enables large file support on the source cluster and all associated target clusters:
# isi_large_file -e
Note: After large file support is enabled on a cluster, the ”cluster full” alert threshold is automatically lowered to 85 percent from the default of 95 percent. This reduction ensures that adequate space is available for large file creation, repair, and restriping.
Step 7: Confirm that large file support is enabled
Run the isi_large_file -l CLI command to confirm that the cluster is now configured to support large files:
# isi_large_file -l
System version: v9.2.0.0
Large file support ready: Yes
Large file support enabled: Yes
Current maximum file size: 16TB
Achievable maximum file size: 16TB
Note: Once large file support has been enabled on a cluster, it cannot be disabled.