Page Comparison

...

1. If freespacegb for the root is -1, it is blocked by configuration for creation of new doc Id’s. (Exception it is the last one)

2. If enough free space is found on the root, it is selected and selection process ends.

3. If not enough free space is found, the next root folder is inspected.

4. In case there is no other root to be processed, the last root with freespacegb limit of -1 will be written until the device is full.

Example:

<repo>.contentservice.splitfilesystemv3.root.1 = C:/Doc_Base 
<repo>.contentservice.splitfilesystemv3.root.2 = C:/Doc_Base_Disk2 
<repo>.contentservice.splitfilesystemv3.root.2.freespacegb=-1 
<repo>.contentservice.splitfilesystemv3.root.3 = C:/Doc_Base_Disk3 
<repo>.contentservice.splitfilesystemv3.root.3.freespacegb=10 
<repo>.contentservice.splitfilesystemv3.root.4 = C:/Doc_Base_Disk4 
<repo>.contentservice.splitfilesystemv3.root.4.freespacegb=50

...

root.3 is only used when C:/Doc_Base_Disk3 has more than 10 GB of disc space available.
root.4 is only used when C:/Doc_Base_Disk4 has more than 50 GB of disc space available and root.3 ha has no more space left..
In case the remaining free space on root.3 and root.4 falls below the limit configured, root.2 is used unit full. Then storing documents will no longer be possiblean exception is thrown and logged. No content can be stored.