Enforcing a placement policy

Article:HOWTO59521  |  Created: 2011-10-12  |  Updated: 2011-10-12  |  Article URL http://www.symantec.com/docs/HOWTO59521
Article Type
How To

Product(s)

Environment

Subject


Enforcing a placement policy

Enforcing a placement policy for a file system requires that the policy be assigned to the file system. You must assign a placement policy before it can be enforced.

See Assigning a placement policy.

Enforce operations are logged in a hidden file, .__fsppadm_enforce.log, in the lost+found directory of the mount point. This log file contains details such as files' previous locations, the files' new locations, and the reasons for the files' relocations. The enforce operation creates the .__fsppadm_enforce.log file if the file does not exist. The enforce operation appends the file if the file already exists. The .__fsppadm_enforce.log file can be backed up or removed as with a normal file.

You can specify the -F option to specify a placement policy other than the existing active placement policy. This option can be used to enforce the rules given in the specified placement policy for maintenance purposes, such as for reclaiming a LUN from the file system.

You can specify the -p option to specify the number of concurrent threads to be used to perform the fsppadm operation. You specify the io_nice parameter as an integer between 1 and 100, with 50 being the default value. A value of 1 specifies 1 slave and 1 master thread per mount. A value of 50 specifies 16 slaves and 1 master thread per mount. A value of 100 specifies 32 slaves and 1 master thread per mount.

You can specify the -C option so that the fsppadm command processes only those files that have some activity stats logged in the File Change Log (FCL) file during the period specified in the placement policy. You can use the -C option only if the policy's ACCESSTEMP or IOTEMP elements use the Prefer criteria.

You can specify the -T option to specify the placement classes that contain files for the fsppadm command to sweep and relocate selectively. You can specify the -T option only if the policy uses the Prefer criteria forIOTEMP.

See the fsppadm(1M) manual page.

The following example uses the fsppadm enforce command to enforce the file placement policy for the file system at mount point /mnt1, and includes the access time, modification time, and file size of the specified paths in the report, /tmp/report.

To enforce a placement policy

  • Enforce a placement policy for a file system:

      # fsppadm enforce -a -r /tmp/report /mnt1
      Current Current  Relocated Relocated
      Class   Volume   Class     Volume    Rule    File
      tier3   vole     tier3     vole      a_to_z  /mnt1/mds1/d1/file1
      tier3   vole     tier3     vole      a_to_z  /mnt1/mds1/d1/file2
      tier3   vole     tier3     vole      a_to_z  /mnt1/mds1/d1/d2/file3
      tier3   volf     tier3     volf      a_to_z  /mnt1/mds1/d1/d2/file4
      .
      .
      .
      Sweep path    : /mnt1
      Files moved   : 42
      KB moved      : 1267
    
    
      Tier Name         Size (KB)   Free Before (KB)    Free After (KB)
      tier4                524288             524256             524256
      tier3                524288             522968             522968
      tier2                524288             524256             524256
      tier1                524288             502188             501227

See Administering placement policies


Legacy ID



uxrt-51sp1_v40222130_v63475671


Article URL http://www.symantec.com/docs/HOWTO59521


Terms of use for this information are found in Legal Notices