Thank you for posting this comment.
The information you mentioned is theoretically correct.
However, basing on our practical tests which were held in our QA lab we can tell that such a limit does not exist for JovianDSS.
Open-E QA team has tested the systems with 500 physical hard drives and such scenarios worked seamlessly.
Moreover, the scenario which included 1000 virtual disks over ISCSI initiator also has been tested and it finished without any problems.

Please note, we are managing disks by using disk-by-id naming convention. That is why the limit can be much more higher.

As an example, we have a Client who has a 2PB’s (petabytes) system in production, where the actual formatted available space is 1.52PB. This solution has been achieved using 280 disks, 8TB each.
Below is the configuration and log dump (zpool_log.txt) showing the actual number of disks used in this system:

1,55 PB formatted
8 un-formatted RAW disk capacity in TB
14 # of data groups
20 # of disks in group
3 # of parity disks
0,91 formatted capacity factor (TB)
0,9 pool max used capacity 155,09
============ ============
1558,51 TB net formatted capacity
1713,60 TB net un-formatted capacity
280 # of disks total
2240 RAW DISK CAPACITY (TB)