Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

An Axiom NAS filesystem will potentially grow in increments up to the value defined as its "Maximum Capacity" setting.	

A FileSystemAlmostFull  alert is raised when the used/current capacity reaches 90% of that value.

Applies to:

Goal

How to handle FileSystemAlmostFull event and is the threshold changeable ?

Fix

The threshold for FileSystemAlmostFull is not user definable but set at 90% by default.

A FileSystemAlmostFull event is generated as a user indication to increase the maximum size permitted.
Once a filesystem has been created it is possible to increase the maximum size of a filesystem (storage class space permitting).

To understand how much space used and increase size please follow below guidance.

A- Display Capacity Usage:

At any time, you can display the actual capacity usage of a filesystem and compare that usage to the total system capacity and assigned capacity limits.
Note: A Pillar Axiom system uses binary units to calculate and display the capacity of physical storage and the size of logical volumes:
1 MB = 1024 x 1024 (1,048,576) bytes
1 GB = 1024 x 1024 x1024 (1,073,741,824) bytes
1 TB = 1024 x 1024 x 1024 x 1024 x 1024 (1,099,511,627,776) bytes

1. Click Storage in the top context pane.
2. Click Usage Summary in the left navigation pane.
In addition to displaying summary usage for the entire system and by type of logical volume, this screen displays a thermometer-style graphic that shows usage by Storage Class.

Here is an example:

B- Display Filesystem Details:

You can display details about all filesystems or you can drill down to the configuration details of a specific filesystem.

1. Click the Storage icon in the top context pane.
2. Click the Filesystems link in the left navigation pane.
3. Review the displayed information to ensure that the filesystem details are what you expect.
4. For additional details of a particular filesystem, click the name of the filesystem.
5. Navigate through the tabbed filesystem pages to review the configuration details.

C- Modify Filesystem Attributes:

Circumstances can arise after you have created a filesystem that require you to change some of its attributes.
For example, you made need to change one or more of these attributes of a filesystem:
● Its name.
● The volume group to which it is assigned.
● The Slammer control unit to which it is assigned.
● Its Quality of Service (QoS) attributes.
● Its write-once, read-many (WORM) capability.

Here we are dealing with a capacity issue which is part of  Quality of Service (QoS) attributes.

To start modify:

1. Click the Storage icon in the top context pane.
2. Click the Filesystems link in the left navigation pane.
3. Select the filesystem that you want to modify.
4. Choose Modify Filesystem from the Actions drop-down list.

You can use Optimizer to identify how much free space the system has prior to increasing its size. To start click "Optimizer" button on Modify screen above. It will show all available resources to you in different configuration options:

Then you can modify desired parameters (Current Capacity, Maximum Capacity, Redundancy etc. ) on above Modify Quality of Service (QoS) attributes screen and click OK to apply.

Changing redundancy or a QoS attribute causes data migration for the filesystem, which can take an extended time to complete during which system performance may be affected.
You will see "Configuring" status on related filesystem while changes applied:

Filesystem status returns to "Optimal" when requested changes are implemented. Please double check with FileSystem details and Usage Summary screens on GUI.

If the filesystem is growing (new writes) then this will also affect replication/snapshot space utilisation.

This solution has no attachment