Unable to remove a Dynamic Storage Tiering (DST) Tier as a placement policy is assigned

book

Article ID: 100026296

calendar_today

Updated On:

Description

Error Message

In the following example, tier 'data_tier2' can not be removed as there is a placement policy in use on that tier. This is the expected behaviour:

  # fsvoladm remove /data data_tier2

UX:vxfs fsvoladm: ERROR: V-3-25686: Volume "data_tier2" is part of a policy, cannot be removed from filesystem /data
UX:vxfs fsvoladm: ERROR: V-3-25572: volume remove failed on /data, Resource temporarily unavailable (11)
 
However, when checking for the existence of the placement policy none is found:
 
 # fsppadm print /data
UX:fsppadm:Error: V-175-50999-142: Placement policy file does not exist for mount point "/data"
 

Cause

 When a placement policy is assigned to a filesystem, the policy is copied into place in the root directory of the filsystem and called '.placement_policy.xml' .

 

 # ls -l /data/.placement_policy.xml

/bin/ls: /data/.placement_policy.xml: No such file or directory

 # fsppadm assign /data policy.xml

UX:fsppadm:Warning: V-175-34615-205: The fcl_keeptime for "/data" is 0 days, policy requires 3 days of filestats. Some IOTEMP and ACCESSTEMP based relocation and deletion may not occur

N8000_01:~/dave # ls -l /data/.placement_policy.xml

-rw------- 1 root root 1615 2012-02-23 06:41 /data/.placement_policy.xml

 
If this file is manually removed the above symptoms occur, whereby the tier can not be removed as a policy exists, but attempting to print the policy errors stating that the policy does not exist.

Resolution

To remove the inconsistency between the 'fsvoladm' and 'fsppadm' commands, reassign the policy and then unasign the policy.

 

 

Check the inconsistency between 'fsvoladm' and 'fsppadm' exists:

# fsvoladm remove /data data_tier2

UX:vxfs fsvoladm: ERROR: V-3-25686: Volume "data_tier2" is part of a policy, cannot be removed from filesystem /data

UX:vxfs fsvoladm: ERROR: V-3-25572: volume remove failed on /data, Resource temporarily unavailable (11)

 # fsppadm print /data

UX:fsppadm:Error: V-175-50999-142: Placement policy file does not exist for mount point "/data"

Clear up the inconsistency by re-assigning the policy and then unasigning it:

 # fsppadm assign /data policy.xml

UX:fsppadm:Warning: V-175-34615-205: The fcl_keeptime for "/data" is 0 days, policy requires 3 days of filestats. Some IOTEMP and ACCESSTEMP based relocation and deletion may not occur

 # fsppadm unassign /data

Now the tier can be succesfully removed:

 # fsvoladm remove /data data_tier2

Confirm the tier has been removed:
 
 # fsvoladm list /data
devid   size                 used                 avail                name
0       208666624            20898614             187768010            data_tier1
 
 

 

Issue/Introduction

When trying to remove a tier from a filesystem that uses DST it is unable to be removed as an active placement policy is in use. However, when checking for the existence of a placement policy none is found.
Powered by Wolken Software