This section describes the
isi_sstore parameters related to
Small Files Storage Efficiency:
list and
stats.
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.
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:
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.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\