Start a Conversation



2 Posts


September 7th, 2023 19:58

Isilon A200 1 node getting full

I have a pool of 4 A200 Nodes and a Pool of 6 H500 nodes in one cluster.

I only have the default File Pool Policy in place.

The Cluster is mainly used for GE PACS.

For some reason one of my A200 nodes sits at 87% full and autobalance jobs will not balance the data out across the other nodes. It will balance all the other nodes in the pool though.

isi status shows all nodes are healthy

Any ideas?

1 Rookie


93 Posts

September 7th, 2023 20:52

When you have an Isilon cluster with unevenly distributed data across the nodes, and auto-balance jobs are not effectively balancing the data on one specific node, there are a few steps you can take to investigate and potentially address the issue:

  1. Check Auto-Balance Settings:

    • Ensure that the auto-balance feature is enabled and configured correctly on your Isilon cluster. You can do this through the OneFS web interface.
  2. Review Data Distribution Policies:

    • Check the data distribution policies for your file pools. Verify that the default policy is distributing data evenly across all nodes in the cluster.
    • Consider creating custom file pool policies if necessary to ensure balanced data distribution.
  3. Check Data Placement Rules:

    • Review the data placement rules to ensure that they are not preventing data from moving to the affected node.
  4. Review Data Usage:

    • Investigate the data usage patterns on the cluster, especially on the node that is 87% full. Identify which directories or shares are consuming the most space. It's possible that certain data types or applications are causing this imbalance.
  5. Data Mobility Policies:

    • Make sure that data mobility policies are not restricting data movement on the affected node. Check if there are specific policies preventing data from being moved.
  6. Run Manual Balance Jobs:

    • Consider running manual balance jobs targeting the specific node that is almost full. You can use the isi job start balance command to initiate a manual balance job for a specific node.
  7. Check for Errors or Alerts:

    • Review the Isilon cluster logs and event notifications for any errors or alerts related to the affected node. This may provide insights into why data isn't balancing as expected.
  8. Monitor Data Growth:

    • Keep an eye on data growth patterns over time. It's possible that the data on the affected node is growing faster than on the other nodes, which can lead to imbalance.
  9. Contact Isilon Support:

    • If you are unable to resolve the issue through the above steps, consider reaching out to Dell EMC Isilon support for assistance. They can provide specialized guidance and may be able to diagnose and address the issue more effectively.

Remember that data balancing in an Isilon cluster can take time, and it's important to monitor the situation periodically to ensure that the data distribution remains balanced across all nodes.

70 Posts

September 11th, 2023 18:21

@ssmith2075 , what does default File Pool Policy say? is H500 supposed to be for hot data and after x amount of time, it goes to A200?

September 12th, 2023 11:56

@Phil.Lam​    this is the only policy in place

Storage settings
Storage target: anywhere
Use SSDs for metadata read acceleration (Recommended)
Snapshot storage target: anywhere
Use SSDs for metadata read acceleration (Recommended)
Using requested protection of the node pool or tier (Suggested)

70 Posts

September 19th, 2023 00:20

@Gatto Sama , point the default storage  target to H500 (hot data)  and then use a file policy to tier it to A2000 (cold data)


No Events found!