PowerScaleOneFS CLI Command Reference

Syntax

isi set 
  [-f -F -L -n -v -r -R] 
  [-p <policy>] 
  [-w <width>] 
  [-c {on | off | endurant_all | coal_only}] 
  [-g <restripe_goal>] 
  [-e <encoding>] 
  [-d <@r drives>] 
  [-a {<default> | <streaming> | <random> | <disabled>| <custom{1..5}>}] 
  [-l {<concurrency> | <streaming> | <random>}] 
  [--nodepool {<id> | <name>}] 
  [-packing {on | off}] 
  [{--strategy | -s} {<avoid> | <metadata> | <metadata-write> | <data>] 
  [--mm-access | -A {on | off}] 
  [--mm-packing {on | off}]   
  [--mm-protection | -P {on | off}] 
  [<file> | <lin>}]

Options

-f

Suppresses warnings on failures to change a file.

-F

Includes the /ifs/.ifsvar directory content and any of its subdirectories. Without -F, the /ifs/.ifsvar directory content and any of its subdirectories are skipped. This setting allows the specification of potentially dangerous, unsupported protection policies.

-L

Specifies file arguments by LIN instead of path.

-n

Displays the list of files that would be changed without taking any action.

-v

Displays each file as it is reached.

-r

Runs a restripe.

-R

Sets protection recursively on files.

-p <policy>

Specifies protection policies in the following forms:

+M

Where M is the number of node failures that can be tolerated without loss of data. +M must be a number from, where numbers 1 through 4 are valid.

+D:M

Where D indicates the number of drive failures and M indicates number of node failures that can be tolerated without loss of data. D must be a number from 1 through 4 and M must be any value that divides into D evenly. For example, +2:2 and +4:2 are valid, but +1:2 and +3:2 are not.

Nx

Where N is the number of independent mirrored copies of the data that will be stored. N must be a number, with 1 through 8 being valid choices.

-w <width>

Specifies the number of nodes across which a file is striped. Typically, w = N + M, but width can also mean the total of the number of nodes that are used.

You can set a maximum width policy of 32, but the actual protection is still subject to the limitations on N and M.

-c {on | off}

Specifies whether write-coalescing is turned on.

-g <restripe goal>

Specifies the restripe goal. The following values are valid:

repair

reprotect

rebalance

retune

-e <encoding>

Specifies the encoding of the filename. The following values are valid:

EUC-JP

EUC-JP-MS

EUC-KR

ISO-8859-1

ISO-8859-10

ISO-8859-13

ISO-8859-14

ISO-8859-15

ISO-8859-160

ISO-8859-2

ISO-8859-3

ISO-8859-4

ISO-8859-5

ISO-8859-6

ISO-8859-7

ISO-8859-8

ISO-8859-9

UTF-8

UTF-8-MAC

Windows-1252

Windows-949

Windows-SJIS

-d <@r drives>

Specifies the minimum number of drives that the file is spread across.

-a <value>

Specifies the file access pattern optimization setting. The following values are valid:

default

streaming

random

custom1

custom2

custom3

custom4

custom5

disabled

-l <value>

Specifies the file layout optimization setting. This is equivalent to setting both the -a and -d flags.

concurrency

streaming

random

--nodepool <id | name>

Sets the preferred nodepool for a file.

--packing {on | off}

<description>

{--strategy | -s} <value>

Sets the SSD strategy for a file. The following values are valid:

If the value is metadata-write, all copies of the file's metadata are laid out on SSD storage if possible, and user data still avoids SSDs. If the value is data, Both the file's meta- data and user data (one copy if using mirrored protection, all blocks if FEC) are laid out on SSD storage if possible.

avoid

Writes all associated file data and metadata to HDDs only. The data and metadata of the file are stored so that SSD storage is avoided, unless doing so would result in an out-of-space condition.

metadata

Writes both file data and metadata to HDDs. One mirror of the metadata for the file is on SSD storage if possible, but the strategy for data is to avoid SSD storage.

metadata-write

Writes file data to HDDs and metadata to SSDs, when available. All copies of metadata for the file are on SSD storage if possible, and the strategy for data is to avoid SSD storage.

data

Uses SSD node pools for both data and metadata. Both the metadata for the file and user data, one copy if using mirrored protection and all blocks if FEC, are on SSD storage if possible.

--mm-access | -A {on | off}

<is this accurate> Specifies whether file access and protections settings should be managed manually.

--mm-packing {on | off}

<is this accurate> Specifies whether file access and protections settings should be managed manually.

--mm-protection | -P {on | off}

<is this accurate> Specifies whether the file inherits values from the applicable file pool policy.

<file> {<lin>}

Specifies a file by LIN.