PowerScale OneFS 9.5.0.0 CLI Administration Guide

Syntax

isi_sstore
[list { -l| -v}]
[stats]

Options

list { -l | -v }

Lists all shadow stores. The -l option displays a summary. The -v option displays more details and can take some time to run depending on the number of shadow stores.

stats

Displays statistics for each shadow store.

Examples

The following is example summary output from isi_sstore list -l.

# isi_sstore list -l
                                                                         
                SIN     lsize     psize  refs filesize         date
4000:0001:0000:0001    516096    828928   126   32632K Jul 11 12:22
4000:0001:0000:0002    368640    681472    90   32632K Jul 11 12:22
4000:0001:0000:0003         0     26112     0   32632K Jul 11 12:22
4000:0001:0000:0004    139264    452096    34   32632K Jul 11 12:22
4000:0001:0000:0005    401408    714240    98   32632K Jul 11 12:22
4000:0001:0000:0006      8192     50688     2   32632K Jul 11 12:22
4000:0001:0000:0007    360448    673280    88   32632K Jul 11 12:22
4000:0001:0000:0008    450560    763392   110   32632K Jul 11 12:22
4000:0001:0000:0009    294912    607744    72   32632K Jul 11 12:22
4000:0001:0000:000a    516096    828928   126   32632K Jul 11 12:22
4100:0001:0000:0000   2654208   4081152   648   32632K Jul 11 12:24

The output includes the following information.

SIN

Identifies the ShadowStore. The SIN number prefix identifies the type of ShadowStore.

• The prefix 0x40 identifies a Container ShadowStore with clone and deduplicated data.
• The prefix 0x41 identifies a Container ShadowStore with packed data.

lsize

Logical size of the ShadowStore, indicating the amount of data contained within.

psize

Physical size.

refs

Total references in the ShadowStore. Includes the number of incoming references to blocks stored in the ShadowStore and references from the ShadowStore.

filesize

The filesize of the ShadowStore. Because ShadowStores often have sparse regions, this metric does not indicate the amount of data contained within. See lsize, above.

• For BSINs, the filesize is set to 2GB when the ShadowStore is created. The space is filled as needed and is never extended.
• For CSINs, the filesize increases as data is added until the size reaches a threshold. Then a new CSIN is created.

date

Creation date of the ShadowStore .

The following is example verbose output from the isi_sstore list -v command:

# isi_sstore list -v
                SIN     lsize     psize         refs filesize         date  sin type underfull frag score efficiency
4000:0001:0000:0001   1163264   5136384          157 2097152K Apr 11 03:22    block         no       0.00       0.23
4000:0001:0001:0000   2777088   6012928          372 2097152K Apr 11 03:23    block         no       0.75       0.46
4000:0001:0002:0000   1433600   5947392         1055 2097152K Apr 11 03:24    block         no       0.00       0.24
4000:0001:0003:0000    163840   2138112           20 2097152K Apr 11 03:24    block        yes       0.00       0.08
4100:0001:0000:0001         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0000:0002         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0000:0003         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0000:0004         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0001:0000         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0001:0001         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0001:0002         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0001:0003         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0001:0004         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0002:0000         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0002:0001         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0002:0002         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0002:0003         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0002:0004         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0003:0000         0     32768            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0004:0000         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0005:0000         0     24576            0   131072 Apr 11 05:18 container       yes       0.00       0.00
4100:0001:0005:0001         0     40960            0   131072 Apr 11 05:18 container       yes       0.00       0.00

All shadow store summary:
Block SINs:
    4 shadow stores
    5537792 (5408 KB) logical bytes
    19234816 (18 MB) physical bytes (including metadata)
    928 (928) incoming refs
Container SINs:
    18 shadow stores
    0 (0 B) logical bytes
    589824 (576 KB) physical bytes (including metadata)
    0 (0) incoming refs

SStores in CStat summary:
Block SINs:
    4 shadow stores
    5537792 (5408 KB) logical bytes

The output includes the following information.

SIN type

One of the following:

• block—the shadow store is used for dedupe or clone operations.
• container—the shadow store is used for packing operations.

underfull flag

If yes, the container is too small to provide storage savings benefits.

frag score

A measure of the level of fragmentation in the shadow store. Higher numbers mean more fragmentation.

The value is the ratio of the sparse blocks in partially allocated stripes to the total size of all stripes containing data.

efficiency score

A ratio of the logical size of the shadow store versus the physical size required to store it (including protection overhead). Higher numbers are better but there will be a limit based on the protection level in use by the shadow stores.

The following is example output from the isi_sstore stats command.

# isi_sstore stats                                                             
Block SIN stats:
6 MB user data takes 3 MB in shadow stores, using 6 MB physical space.
280K physical average per shadow store.

2 refs per block.
Reference efficiency 50%.
Storage efficiency 200% 

Container SIN stats:
3 MB user data takes 3 MB in shadow stores, using 4 MB physical space.
3984K physical average per shadow store.

1 refs per block.
Reference efficiency 0%.
Storage efficiency 100%
Raw counts={ type 0 num_ss=20 lsize=3055616 pblk=715 refs=1119 }
{ type 1 num_ss=1 lsize=2654208 pblk=498 refs=648 }

The first set of statistics is for a shadow store that contains cloned data. The Storage efficiency of 200% means that every two files consume one file space after cloning.

The second set of statistics is for a shadow store that contains packed data. Because packed data is single-referenced, its Storage efficiency is 100% and its Reference efficiency is 0% (that is, no block sharing).

The Raw counts field at the end of the output contains the following statistics:

num_ss

The number of ShadowStores.

lsize

Logical size of data contained in the ShadowStores.

pblk

Number of physical blocks.

refs

Number of incoming block references for the shadow store.