From a command line perspective, we allow a maximum of 1025 characters for an argument from memory. As the pathset list is one argument (each separated by commas but essentially a single string), the argument needs to be 1025 characters or less.
So from this perspective, the following command would succeed, as an example:
If you have more paths to add than the 1025 character limit, you can use 'compression physical-capacity-measurement test1 add paths ' to add more paths.
I'll need to look into if there is a hard limit, if you really need the maximum limit, but inhouse, I've attempted to add 300 paths to a single Mtree without issue. Please let me know.
and so on. How many of these test* pathsets can i create ? Reason i want to have a pathset per path is because when you run the report that consists of multiple paths per pathset you get a combined report. What i am looking for is report for each individual path.
OK, so regarding the number of pathsets - well we don't actually have an explicit maximum per se. Let me explain why.
In previous DDOS releases, this type of information was held in a proprietary format in a pre-allocated flat file. There was a file for what we will call 'top level registry', i.e. vtl, replication, configuration, security, system e.t.c. Each of these top level registries were sized independently, judging by what the registry was used for, i.e. vtl registry was larger as this could potentially store a large number of pools/tapes. This meant we had a certain maximum number of entries that could be stored in one of the top level registry areas.
In later releases, (from DDOS 5.6 iirc), we have moved to a database format for storing the registry, for a number of reasons, but one of these is being able to grow (and shrink) the registry when required.
So in the case of pcr, we store this in the 'config_master.pcr' part of the registry.
In SE mode, you can view the registry stats with the 'reg show stats' command, although this is really meant for support/engineering use as customers don't really view/modify the registry directly unless explicitly directed.
The 'config_master' top level registry, is initially sized at 128KB, which we can see from the following extract:
=================================================
# reg show stats
Registry Fill Statistics
Registry Bytes Stored Perc Entries Stored Perc GenId
As you can see from the above, the number of bytes I'm currently using is 92492 and have 1438 registry entries which accounts for 70% of the 128KB (131072 bytes) allocated space.
So how does this relate to PCR? Well each time we add a pathset, we store this under 'config_master' in the PCR subset, which full name is 'config_master.pcr' as mentioned above. So as we add more pathset entries, the config_master file/table will grow accordingly.
So for example, I added 2000 pathsets, which has caused the registry to grow as follows:
=================================================
# reg show stats
Registry Fill Statistics
Registry Bytes Stored Perc Entries Stored Perc GenId
The reason it's grown to 9408, is that each pathset will create 4 registry entries (and it's a shared system so other things are ongoing) - but it was just an example.
richbinstead
62 Posts
1
October 28th, 2016 04:00
Hi Dynamox,
From a command line perspective, we allow a maximum of 1025 characters for an argument from memory. As the pathset list is one argument (each separated by commas but essentially a single string), the argument needs to be 1025 characters or less.
So from this perspective, the following command would succeed, as an example:
==================================================
sysadmin@DDOS57# compression physical-capacity-measurement pathset create test1 paths /data/col1/repl-dr/1,/data/col1/repl-dr/2,/data/col1/repl-dr/3,/data/col1/repl-dr/4,/data/col1/repl-dr/5,/data/col1/repl-dr/6,/data/col1/repl-dr/7,/data/col1/repl-dr/8,/data/col1/repl-dr/9,/data/col1/repl-dr/10,/data/col1/repl-dr/11,/data/col1/repl-dr/12,/data/col1/repl-dr/13,/data/col1/repl-dr/14,/data/col1/repl-dr/15,/data/col1/repl-dr/16,/data/col1/repl-dr/17,/data/col1/repl-dr/18,/data/col1/repl-dr/19,/data/col1/repl-dr/20,/data/col1/repl-dr/21,/data/col1/repl-dr/22,/data/col1/repl-dr/23,/data/col1/repl-dr/24,/data/col1/repl-dr/25,/data/col1/repl-dr/26,/data/col1/repl-dr/27,/data/col1/repl-dr/28,/data/col1/repl-dr/29,/data/col1/repl-dr/30,/data/col1/repl-dr/31,/data/col1/repl-dr/32,/data/col1/repl-dr/33,/data/col1/repl-dr/34,/data/col1/repl-dr/35,/data/col1/repl-dr/36,/data/col1/repl-dr/37,/data/col1/repl-dr/38,/data/col1/repl-dr/39,/data/col1/repl-dr/40,/data/col1/repl-dr/41,/data/col1/repl-dr/42,/data/col1/repl-dr/43,/data/col1/repl-dr/44,/data/col1/repl-dr/45,/data/col1/repl-dr/46,/data/col1/repl-dr/47
Pathset "test1" created.
==================================================
however the following command would fail as it exceeds the 1025 character limit:
==================================================
sysadmin@DDOS57# compression physical-capacity-measurement pathset create test1 paths /data/col1/repl-dr/1,/data/col1/repl-dr/2,/data/col1/repl-dr/3,/data/col1/repl-dr/4,/data/col1/repl-dr/5,/data/col1/repl-dr/6,/data/col1/repl-dr/7,/data/col1/repl-dr/8,/data/col1/repl-dr/9,/data/col1/repl-dr/10,/data/col1/repl-dr/11,/data/col1/repl-dr/12,/data/col1/repl-dr/13,/data/col1/repl-dr/14,/data/col1/repl-dr/15,/data/col1/repl-dr/16,/data/col1/repl-dr/17,/data/col1/repl-dr/18,/data/col1/repl-dr/19,/data/col1/repl-dr/20,/data/col1/repl-dr/21,/data/col1/repl-dr/22,/data/col1/repl-dr/23,/data/col1/repl-dr/24,/data/col1/repl-dr/25,/data/col1/repl-dr/26,/data/col1/repl-dr/27,/data/col1/repl-dr/28,/data/col1/repl-dr/29,/data/col1/repl-dr/30,/data/col1/repl-dr/31,/data/col1/repl-dr/32,/data/col1/repl-dr/33,/data/col1/repl-dr/34,/data/col1/repl-dr/35,/data/col1/repl-dr/36,/data/col1/repl-dr/37,/data/col1/repl-dr/38,/data/col1/repl-dr/39,/data/col1/repl-dr/40,/data/col1/repl-dr/41,/data/col1/repl-dr/42,/data/col1/repl-dr/43,/data/col1/repl-dr/44,/data/col1/repl-dr/45,/data/col1/repl-dr/46,/data/col1/repl-dr/47,/data/col1/repl-dr/48
**** Too many arguments.
Incomplete syntax "compression physical-capacity-measurement pathset create test1 paths /data/col1/repl-dr/1 /data/col1/repl-dr/2 /data/col1/repl-dr/3 /data/col1/repl-dr/4 /data/col1/repl-dr/5 /data/col1/repl-dr/6 /data/col1/repl-dr/7 /data/col1/repl-dr/8 /data/col1/repl-dr/9 /data/col1/repl-dr/10 /data/col1/repl-dr/11 /data/col1/repl-dr/12 /data/col1/repl-dr/13 /data/col1/repl-dr/14 /data/col1/repl-dr/15 /data/col1/repl-dr/16 /data/col1/repl-dr/17 /data/col1/repl-dr/18 /data/col1/repl-dr/19 /data/col1/repl-dr/20 /data/col1/repl-dr/21 /data/col1/repl-dr/22 /data/col1/repl-dr/23 /data/col1/repl-dr/24 /data/col1/repl-dr/25 /data/col1/repl-dr/26 /data/col1/repl-dr/27 /data/col1/repl-dr/28 /data/col1/repl-dr/29 /data/col1/repl-dr/30 /data/col1/repl-dr/31 /data/col1/repl-dr/32 /data/col1/repl-dr/33 /data/col1/repl-dr/34 /data/col1/repl-dr/35 /data/col1/repl-dr/36 /data/col1/repl-dr/37 /data/col1/repl-dr/38 /data/col1/repl-dr/39 /data/col1/repl-dr/40 /data/col1/repl-dr/41 /data/col1/repl-dr/42 /data/col1/repl-dr/43 /data/col1/repl-dr/44 /data/col1/repl-dr/45 /data/col1/repl-dr/46 /data/col1/repl-dr/47 /data/col1/repl-dr/48", showing help:
compression physical-capacity-measurement pathset create
paths
[measurement-retention { | default}]
Add a new pathset
==================================================
If you have more paths to add than the 1025 character limit, you can use 'compression physical-capacity-measurement test1 add paths ' to add more paths.
I'll need to look into if there is a hard limit, if you really need the maximum limit, but inhouse, I've attempted to add 300 paths to a single Mtree without issue. Please let me know.
cheers, RIch.
dynamox
9 Legend
•
20.4K Posts
0
November 2nd, 2016 11:00
Hello Rich,
thank you for your reply. I am actually interested in the number of individual pathsets, not paths per pathset. For example:
compression physical-capacity-measurement pathset create test1 paths /data/col1/repl-dr/1
compression physical-capacity-measurement pathset create test2 paths /data/col1/repl-dr/2
compression physical-capacity-measurement pathset create test3 paths /data/col1/repl-dr/3
and so on. How many of these test* pathsets can i create ? Reason i want to have a pathset per path is because when you run the report that consists of multiple paths per pathset you get a combined report. What i am looking for is report for each individual path.
Thank you
richbinstead
62 Posts
0
November 3rd, 2016 04:00
Hi Dynamox,
Apologies. My fault as I mis-read your post.
OK, so regarding the number of pathsets - well we don't actually have an explicit maximum per se. Let me explain why.
In previous DDOS releases, this type of information was held in a proprietary format in a pre-allocated flat file. There was a file for what we will call 'top level registry', i.e. vtl, replication, configuration, security, system e.t.c. Each of these top level registries were sized independently, judging by what the registry was used for, i.e. vtl registry was larger as this could potentially store a large number of pools/tapes. This meant we had a certain maximum number of entries that could be stored in one of the top level registry areas.
In later releases, (from DDOS 5.6 iirc), we have moved to a database format for storing the registry, for a number of reasons, but one of these is being able to grow (and shrink) the registry when required.
So in the case of pcr, we store this in the 'config_master.pcr' part of the registry.
In SE mode, you can view the registry stats with the 'reg show stats' command, although this is really meant for support/engineering use as customers don't really view/modify the registry directly unless explicitly directed.
The 'config_master' top level registry, is initially sized at 128KB, which we can see from the following extract:
=================================================
# reg show stats
Registry Fill Statistics
Registry Bytes Stored Perc Entries Stored Perc GenId
--------------- ------- ------ ---- ------- ------ ---- ------
...
...
config_master 131072 92492 70% 1438 1438 100% 8179
...
...
=================================================
As you can see from the above, the number of bytes I'm currently using is 92492 and have 1438 registry entries which accounts for 70% of the 128KB (131072 bytes) allocated space.
So how does this relate to PCR? Well each time we add a pathset, we store this under 'config_master' in the PCR subset, which full name is 'config_master.pcr' as mentioned above. So as we add more pathset entries, the config_master file/table will grow accordingly.
So for example, I added 2000 pathsets, which has caused the registry to grow as follows:
=================================================
# reg show stats
Registry Fill Statistics
Registry Bytes Stored Perc Entries Stored Perc GenId
--------------- ------- ------ ---- ------- ------ ---- ------
...
...
config_master 509398 509398 100% 9408 9408 100% 10349
...
...
=================================================
The reason it's grown to 9408, is that each pathset will create 4 registry entries (and it's a shared system so other things are ongoing) - but it was just an example.
I hope that helps answer your question?
cheers, Rich.