Content Comparison

...

Netapp v3 is implemented since tia core 3.5. It is based on SFS v3.

Locking only works if retention service (tC) is configured.

The NetApp type can also be used for ICAS.

...

<repoName>.contentservice.type=netappv3
<repoName>.contentservice.netappv3.root.0 = C:/DEV/cs/storage_autodigit_sfs0
<repoName>.contentservice.netappv3.root.0.FreeSpaceGb=30
<repoName>.contentservice.netappv3.root.1 = C:/DEV/cs/storage_autodigit_sfs1
<repoName>.contentservice.netappv3.root.1.FreeSpaceGb=-1
<repoName>.contentservice.netappv3.root.2 = C:/DEV/cs/storage_autodigit_sfs2
<repoName>.contentservice.netappv3.root.2.FreeSpaceGb=40
#<repoName>.contentservice.netappv3.ContrepInPath = #default: false
#<repoName>.contentservice.netappv3.RetriesFolderCreate = #default: 3
<repoName>.contentservice.netappv3.maxfolderblocks=8
<repoName>.contentservice.netappv3.maxFileNameLength=200
<repoName>.contentservice.netappv3.rootSelectionIntervalH=9

• Version 3 brings these changes compared to v2

  • the folder block size is not fixed 4 anymore. It can be choosen: 4, 8, 16. With this change the storage folder depth can be reduced.

  • the file name length can be limited. In v2 there was no limit.

  • multiple roots are supported. They are used until the free space limit is arrived. Then it choses the next in order.

root folder selection behavior

• the algorithm tries in numbers order to pick the root

  • it checks the available space and compares it with the given limit. Default limit is 10GB.

  • If the algorithm finds out, that a root hasn’t enought space it tries the next.

  • with limit -1 a drive can be blocket. It is then used in read only state (and / or only for adding components and infos)

• the algorithm is triggered by:

  • if rootSelectionIntervalH is exceeded

  • if IOException had happen while IO operation