Welcome To
X-RAID Volume Calculator - Site Edition - v2.11
By: infotinks, Updated: 2022-03-19
*
Go Home to infotinks
*** MAINTAINER:
boss@infotinks.com
(if you encounter errors or the site isnt working, please email me)
***
Everything here is based on my own opinion - Ill say it again in another note, dont take everything you see here as 100% accurate - there might be mistakes in my algorithms as the systems get more and more complex - and if you encounter any mistakes please let me know via my email above. Also I cant stress enought, do your own research, also read my notes. I might be missing key factors/notes in here that to me seem obvious, but to others are not, so please let me know where I need to be more clear, and where I need to be less clear. So again do your research. Research RAIDs, BTRFS, ZFS, EXT, its all for the best, we are all in IT together. In my opinion, call Netgear Sales when doing a big purchase, the sales team can pick the best product for your scenerio/use-case.
* NOTE: All results are just estimates, so you cannot sue me if they dont match - ALSO PLEASE READ ALL THE NOTES
* NOTE: RN is for ReadyNAS, RD is for ReadyDATA
* NOTE: Here is a
btrfs calculator by carfax
that has similar mechanics to xraid. It helps visualize how the different sized drives get split into regions (partitions on the NAS) and how btrfs can intellegintly raid it. The ReadyNAS does this as well using XRAID RAID5 and XRAID RAID6 technology, which is accomplished thru a combo or partitions + mdadm + ext4 or btrfs. ext on ReadyNAS 4.x and 5.x and btrfs on ReadyNAS 6.x. This online tool helps visualize these regions and partitions as they are seperated by different colors. It gives you the raw size in GB or TB. However my calculator converts to GiB and TiB and also takes into account filesystem and other overhead, so it comes out closer to the expected value (with respect to ReadyNAS).
For ReadyNAS 6 (aka OS 6):
The new ReadyNAS 6.x uses X-RAID with huge differences at the higher layers, BTRFS (used for volume management and the filesystem in OS 6) instead of LVM & EXT (LVM used for volume management and EXT used as filesystem in ReadyNAS RAIDiator 4 and 5).
Thus the EXT filesystem limitations mentioned in the below
Notes DO NOT APPLY for the ReadyNAS 6.x devices.
Just select "Intel" or "ARM" tfrom the Architecture list below, even though the Architecture list is for the ReadyNAS 5.x, the calculations of storage space come out to be close.
Also leave the SNAPSHOT SIZE at 0 for ReadyNAS 6.x calculations, because they are handled completely differently.
Anyhow FINAL RESULTS MAY BE + or - 10% OFF, CANT SUE IF INCORRECT/WRONG.
For ReadyDATA (aka RD):
The ReadyDATA units use Unix based OS, unlike the ReadyNAS which uses a Linux based OS. ReadyDATAs use a Copy on Write filesystem which does volume management (This is similar to OS 6s, BTRFS which is a COW FS thats also a volume manager). ReadyDATA uses ZFS, instead of BTRFS. ZFS operates completely differently then BTRFS. Therefore there are a few changes. For one we dont have SWAP space in ReadyDATA (instead we just have alot of RAM). Also volumes in ZFS are split into VDEVS (drives are pooled into VDEVS), each VDEV is connected together to another VDEV via RAID 0 like algorithm. Each VDEV should be the same size (Same number of storage drives in each VDEV -
With ReadyDATA calculations its only realistic to put the same type & therefore size of drive in each VDEV, so do not have varying size drives in a VDEV
. Also performance enhancing drives like ZIL or ARC do not count -
Do not put your ZIL/Write Cache & ARC/Read Cache & Global Spare drive sizes in the drive slot textboxs, which you will see in Step 3 below, instead only account the drives which give you storage space
). As an example I have a system with 24 storage drives (and any number of performance enhancing drives), that is split into 3 VDEVs. So Each Vdev evenly has 8 drives. Lets assume each VDEV is RAID 6. So VDEV1 which has 8 drives, provides me with 6 drives of storage, 2 drives of parity. Same with VDEV2 and VDEV3. So if we are using 1TB drives. VDEV1,2,3 each give me 6TB. The total volume gives me 6TB * 3 = 18 TB. You can lose 2 drives out of each VDEV. If one of those VDEVS goes offline then the whole volume goes offline. So I could lose 2 drives out of VDEV1 and still be okay. I could lose 2 drives out of VDEV1,2 and 3 and still be okay (6 drives lost). As soon as I lose 3 drives in any of the VDEVs the whole volume goes offline. (in case of drive failures, the ReadyDATA does work with hot-replace and also global-spares)
The calculations here apply to a single vdev but with a MULTIPLIER field can apply to the whole volume, to get the correct answer fill out the MULTIPLIER field which should beequal to the number of VDEVS
One assumption is made that each VDEV in the volume has the same number of storage drives (that is a strict rule, but it can have rare exceptions). In the case that you have assymetric VDEVs (where each vdev has a different number of storage drives), then calculate the size of each VDEV individually (using multiplier of value 1), then add up the TOTALs on a piece of paper to get your final result. To find out the number of drives in each of your VDEVS run the following command "
zpool status
" (you can also see the output of this command in the logs)
ReadyNAS vs ReadyDATA
Everything here is all opinion - my opinion - dont take my word for granted, do your own research, call Netgear Sales team, etc
- Both the ReadyNAS and ReadyDATA are great storage products. Not only for the dollar, but also as a complete unit. Here Im comparing ReadyNAS OS 6 to ReadyDATA. Both use state of the art Copy-on-write filesystems. For both systems the developers listen to the customer.
So what should I get?
- If your looking to use iSCSI and need to have a live continous backup of your data. Where you need the source and destination to be in constant sync (Realistically due to limitations of the physical world we live in and the speed of packets in a wire, the data in a Destination can only be a few minutes behind the source unit, when units are in-sync). I recommend the ReadyDATA for that. Using the state of the art Replicate service. (NOTE: Replicate exists for both ReadyDATA and ReadyNAS, although their GUIs are similar, the backend code is completely different. Current the ReadyDATA supports live iSCSI replication.)
- If you dont need that, then I recommend either or. The ReadyDATA currently comes in two flavors RDD516 and RD5200, both are enterprise ready products. The ReadyNAS OS 6 comes in many more flavors that will due for simple filestorage with somme units (RN2120, RN1XX), up to enterprise storage with other units (RN3XXX, RN4XXX).
- Here is a link that covers the features of both pretty well:
Whitepaper on ReadyNAS and ReadyDATA
Start By selecting your Netgear Storage Architecture (Select the type of ReadyNAS, or ReadyDATA) and filling out any applicable variables (snapshots & disk sizes)
(Step 1)
Please select
Architecture
Type:
ReadyNAS: Intel, X86 (RN Firmware 4.2.x / RAIDiator 4, and OS 6)
ReadyNAS: ARM (ReadyNAS RAIDiator 5.x, and OS 6)
ReadyNAS: SPARC (ReadyNAS Firmware 4.1.x)
ReadyDATA (RD Firmware 1.x.x)
For ReadyNAS 6.x use Intel or ARM depending on unit.
(Step 2)
Snapshot
Size (between 0 and 100 GB) [GiB, base 2]:
For ReadyNAS OS 6 & ReadyDATA use 0 GB snapshot (
So just skip this step for ReadyNAS OS 6 and ReadyDATA
). This is meant for units which you have to initialize the snapshot size when you setup the unit at Factory default (so the 4.1.x, 4.2.x, and 5.x - the units which use EXT and LVM). We use 0 for the ReadyDATA and ReadyNAS 6.x, because those units use ZFS and BTRFS, respectively. ZFS or BTRFS are used for volume management and as filesystem together ZFS and BTRFS do not require pre-allocating space for snapshots during initialization of the device (during Factory default).
Info about Step 3:
Fill the Slots with Drive (Using drive sizes that the manufacturers reports, so in base 10, i.e. 1 KB = 1000 bytes). The units are in GB. If you put "1" that means 1 GB or 1,000,000,000 bytes. So if you put "3000" thats 3000 GB, that would be your typical 3 TB drive, which is about 3,000,000,000,000 bytes. If you have multiple RAID Groups, fill the slots up the same as you would fill up 1 RAID Group - and not all the RAID Groups. The vdev/multiplier/number of RAID groups field will take care of the multiplicity effect of RAID Groups.
Note 1:
Use drive sizes that are listed on the compatability list on ReadyNAS.com
So far those sizes [in GB base 10] that are supported: 500, 750, 1000, 1500, 2000, 3000, 4000, 6000
In this app you can put in other sizes but Netgear only recommends and supported drives listed in the compatability list
* ReadyNAS COMPATIBILITY LIST:
ReadyNAS HardDrive Compatibility List
* ReadyDATA SUPPORTED DRIVE PACKS:
ReadyDATA Disk Packs (The only Compatible Drives)
NOTE:
ReadyDATA only supports the disks in the disk packs, this is to maximize performance
Note 2:
If you have a HOT SPARE, leave it out of the calculation, it picks the biggest drive and 0s it on the calculation.
To emulate a HOT SPARE - For example in a system with three 1TB and one 2TB drive. Just put into the app the three 1TB drives.
To clear all the values just Refresh the page or press F5 on your keyboard
(Step 3)
Fill the Slots [of a
Single
VDEV/
RAID Group
] with
Drives
:
Fill these slots up to match your VDEV/RAID Group (assuming all your vdevs have the same number of storage drives - if you have VDEVS in the same volume with different number of storage drives - to emphasize again, performance enhancing cache drives dont count as storage increasing drives. In the case that you have different number of storage drives in your VDEVS -ex VDEV1 has 5 drives, and VDEV2 has 4 DRIVES, calculate each vdev manually using this calculator, leave the vdev multiplier counter below at 1, and then add up the numbers manually). After filling out this single VDEV in the next step use the multiplier/vdev/RAID Group field to tell the calculator how many of these VDEVS you have (Again only use the multiplier if each VDEV has the same number of storage drives - and again, performance enhancing cache drives dont count as storage increasing drives - what do you do if each VDEV/RAID Group has different number of Storage Drives? Calculate each VDEV seperately and add up the totals.)
If your NAS doesnt support RAID Groups/VDEVs then that means you only have 1 VDEV/RAID Group, simply ignore the fields/text that mentions VDEVS/RAID Groups.
For units use GBs of the Manufacturer's provided Drive Size [GB, base 10]
Gigabytes = 1,000,000,000,000 bytes or 1 KB = 1000 Bytes
So base 10 units (ex:
for 3 TB drives, just put 3000
)
Put 0 for empty slots
Select
12
,
60
or
Any Drives
to start configuring the drives
12 Drives
60 Drives
Any Drives
Drive 1 [GB]:
Drive 2 [GB]:
Drive 3 [GB]:
Drive 4 [GB]:
Drive 5 [GB]:
Drive 6 [GB]:
Drive 7 [GB]:
Drive 8 [GB]:
Drive 9 [GB]:
Drive 10 [GB]:
Drive 11 [GB]:
Drive 12 [GB]:
Drive 1 [GB]:
Drive 2 [GB]:
Drive 3 [GB]:
Drive 4 [GB]:
Drive 5 [GB]:
Drive 6 [GB]:
Drive 7 [GB]:
Drive 8 [GB]:
Drive 9 [GB]:
Drive 10 [GB]:
Drive 11 [GB]:
Drive 12 [GB]:
Drive 13 [GB]:
Drive 14 [GB]:
Drive 15 [GB]:
Drive 16 [GB]:
Drive 17 [GB]:
Drive 18 [GB]:
Drive 19 [GB]:
Drive 20 [GB]:
Drive 21 [GB]:
Drive 22 [GB]:
Drive 23 [GB]:
Drive 24 [GB]:
Drive 25 [GB]:
Drive 26 [GB]:
Drive 27 [GB]:
Drive 28 [GB]:
Drive 29 [GB]:
Drive 30 [GB]:
Drive 31 [GB]:
Drive 32 [GB]:
Drive 33 [GB]:
Drive 34 [GB]:
Drive 35 [GB]:
Drive 36 [GB]:
Drive 37 [GB]:
Drive 38 [GB]:
Drive 39 [GB]:
Drive 40 [GB]:
Drive 41 [GB]:
Drive 42 [GB]:
Drive 43 [GB]:
Drive 44 [GB]:
Drive 45 [GB]:
Drive 46 [GB]:
Drive 47 [GB]:
Drive 48 [GB]:
Drive 49 [GB]:
Drive 50 [GB]:
Drive 51 [GB]:
Drive 52 [GB]:
Drive 53 [GB]:
Drive 54 [GB]:
Drive 55 [GB]:
Drive 56 [GB]:
Drive 57 [GB]:
Drive 58 [GB]:
Drive 59 [GB]:
Drive 60 [GB]:
Please fill out this field Accordingly
TODO: FILL-IN-STUFF-HERE
(Step 4)
Multiplier (number of
vdevs / number of RAID groups
):
- If you dont know what this does just leave this as 1 (the default value). Also this number should always be an INTEGER and not have a DECIMAL (although the calculation will still work if its a decimal number is given).
- This is a multiplier field. It will just multiply all of the answers by this number. This is useful if you have multiple vdevs. For ReadyNAS 4.1.x & 4.2.x & 5.x use 1 (1 is the default). For ReadyNAS 6.x use 1 (unless you have done vdev horizontal expansions). For ReadyDATA this is the number of vdevs you have. Running "
zpool status
" from SSH (SSH is not supported under warranty) can show you the number of vdevs in your volumes, and the number of drives in each vdev.
- NOTE:
If you have multiple VDEVs & thus a multiplier bigger than 1, please make sure each vdev is the same size (same number of storage drives - performance enhancing drives such as ZIL or ARC do not count), also when you do the calculation make sure you fill out STEP 3, the drives, as you have a single vdev (not the whole unit).
- EXAMPLE:
if you have a 24 drive array (each drive 4 TB) that is made of 3 vdevs. Then fill out STEP 3 with 8 drives (24 divided 3) of size 4000 each (4 TB), and here put 3 for the multiplier.
-
KEY EXAMPLE:
When you expand a ReadyDATA volume from a volume that is 5 drives in a RAID 5, you have 1 VDEV/RAID group, then you add 5 more drives to your ReadyDATA, and you expand the initial volume, creating a 2nd VDEV. So now you have 10 drives of 2 VDEVS each housing 5 drives - we call this RAID 50x2. Now take another 5 drives and expand that same initial volume, now you have RAID 50x3, which has 15 drives (3 vdevs, each with 5 drives). Each of those vdevs gives you 1 drive for parity, and 4 drives for storage capacity. So in total after the 2 expansions, aka RAID 50x3, you have 4*3=12 storage drives, and 1*4 parity drives. You can lose up to 4 drives, considering they only fail in different vdevs. A better way to see it, is you can only lose up 1 drive in each of the 3 VDEVS and still have your volume running. As soon as you lose 2 drives in any VDEV that will go up to. Of course in RAID 60x3 you can lose up to 2 drives and no more per VDEV, for a total of 2*3=6 parity drives that you can lose. (dont think that any individual drive holds the parity, each drive holds parity, the parity stripes with ZFS are dynamic and variable and spread across each drive, this variability fixes alot of issues of traditional RAID 5.). If you lose more than 1 drive in a vdev in RAID 5, or 2 drives in a vdev in RAID 6, your volume goes offline and you can use data recovery services to see if Netgear can recover your data.
(Step 5)
Press this
to calculate the result or just press
Enter Key
NOTE:
switching between fields will also update the results
IMPORTANT:
RAID 5 for all intensive purposes means SINGLE DISK REDUNDANCY and RAID 6 means DUAL DISK REDUNDANCY
#########################
==RESULTS (Will go below):==
#########################
Note 3: What goes into the Calculation?
* For Both:
- The first calculation that takes place is finding out the RAID Space, which is just the amount of storage we get to work with after taking into account parity space or mirroring. This number is the basis for the next calculation which is the "Final Filesystem" size
- The biggest cost of volume size (when you reading the "Final Filesystem size") is in conversion from base 10 size to base 2. Drive manufacturers label 1 TB but actually mean 0.9 TB based on the base 2 to 10 conversion. In my opinion this isnt really a cost, but just a conversion, but since the units have close to the same name GB/TB vs GiB/TiB, this is why you feel cheated when you purchase a 3TB drive and only find out you have 2.7 TiB to work with. In reality you still have 3TB, and you still have 2.7 TiB, its just a different way to look at things (like Celsius vs Fahrenhiet, which tell the same story in a different language)
- After the conversion takes place, the proper overheads are taken out. These are different depending on what Architecture your using.
* For ReadyNAS:
- Each calculation (when you reading the "Final Filesystem size") takes into account OS & SWAP partition costs per each disk, the snapshot size across the whole volume, and the RAID overhead across the whole volume.
* For ReadyDATA:
- Each calculation (when you reading the "Final Filesystem size") takes into account OS Size per volume, along with some RAID overhead. Snapshot space is not calculated as that is not preallocated at initialization of the unit.
Note 4: What values to read?
To get a close estimate (in units of GB/TB base 10):
* Read the "RAID Space" values to get a close approximation of the drive space available to the unit. This takes into account all of the parity and mirroring that will take place.
To get a real world approximation to what the user will see (in units of GB/TB base 2):
* Read the "Final Filesystem Size" values to get a close approximation of what the user will see. This will be in units of GiB and TiB - base 2 (which is how all space is presented while you use a computers), so the user will get a better sense of actual useable space. Also this value takes into account any other overhead (RAID overhead, OS size, snapshot size)
* With 1 disk - the given "Final Filesystem Size" value is correct.
* With 2 disks - X-RAID converges to RAID 1, read the "Final Filesystem Size with RAID 5" for correct the result. (Why? programmatically RAID 5 and RAID 1 calculations are equal and correct with this algorithm)
* With 3 disks - X-RAID converges to RAID 5, read the "Final Filesystem Size with RAID 5" calculation for correct result.
* With 4+ disks - X-RAID converges to RAID 5 or 6 based on your selection on the Volume Settings tab of Frontview, so read "Final Filesystem Size with RAID 5" or "... 6" depending on your setup.
Note 5a:
ReadyNAS Expansion Limitations of the EXT Filesystem (Only Applies to ReadyNAS RAIDiator 4.x and RAIDiator 5.x - not to RN OS 6 & ReadyDATA)
(1)
An expansion that causes the Filesystem to increase 8 TB since the last Factory Default will fail.
(2)
An expansion that causes the Total Filesystem size to be 16 TB or more after the expansion will fail.
* These sizes refer to the Filesystem Sizes, not raw disk space.
* The solution/workaround for this is to Factory Default with the final volume in place.
* These are not ReadyNAS limitations, but more of Linux Kernel and EXT Filesystem Limitations.
Note 5b:
ReadyNAS Expansion Limitations of the BTRFS Filesystem (Only Applies to RN OS 6 units)
Check the Release notes & the Manual for any limitations, but you will see that the ReadyNAS OS 6 is unlimited in the scope of expansions and volume sizes.
(1)
There are no limitations on the Intel units. Just can't go over the BTRFS limitations of 14 EiB max file & volume size (grabbed from
Wikipedia's BTRFS page
).
(2)
The ARM units do have a limitation that is brought on by the ARM processor (Intel versions of the RN OS 6 do not experience these). These are seen in the "Limitations" list of ReadyNAS firmware release note (specifically here Im looking at the firmware 6.2.0 release note). These are not Filesystem limitations, but CPU limitations:
ReadyNAS OS 6 6.2.0 Release Notes
- (a)
ReadyNAS 102, 104, and 2120 only support creating iSCSI LUNs 8TB and smaller.
- (b)
ReadyNAS 102, 104, and 2120 only support volumes up to 16TB.
Note 5c:
ReadyDATA Expansion Limitations of the ZFS Filesystem (Only Applies to ReadyDATA units)
Check the Release notes & the Manual for any limitations on expansion or final volume size.
- Maximum size of a volume is listed as 256 Zebibytes, and 16 exbibytes for max filesize as seen on
Wikipedia's ZFS page
)
Note 6a:
Can NOT Add SMALLER Drives (Only Applies to ReadyNAS)
When you click CALCULATE above it assumes that this is a fresh start, as if you factory defaulted with that set of disks.
The reason I mention this is because adding SMALLER disks to the disk set works out in this calculator
HOWEVER, in a live unit you cannot add SMALLER disks they would be unused, the partitioning will not work out the new disks would be unused
What do I mean by SMALLER disks?
Example, if your system only has 2 TB and 3 TB disks, do not add a 1 TB disk.
The WORKAROUND for the system to accept the SMALLER disks is to backup your data and factory default with all disks put in place
The BEST SOLUTION in my opinion is to only add bigger disks, or new disks equal in size to any of the disks operating in the system
Note 6b:
Can NOT Add INBETWEEN Drives (Only Applies to ReadyNAS)
When you click CALCULATE above it assumes that this is a fresh start, as if you factory defaulted with that set of disks.
The reason I mention this is because adding INBETWEEN disks to the disk set works out in this calculator
HOWEVER, in a live unit you cannot add INBETWEEN disks they would be unused, the partitioning will not work out
What do I mean by INBETWEEN disks?
Example, if your system only has 1 TB and 3 TB disks, do not add a 2 TB disk.
The WORKAROUND for the system to accept the INBETWEEN disks is to backup your data and factory default with all disks put in place
The BEST SOLUTION in my opinion is to only add bigger disks, or new disks equal in size to any of the disks operating in the system
Note 7a:
X-RAID 1 vs. X-RAID 2 (Only Applies to ReadyNAS)
* X-RAID 1 is used in the 4.1.x (and old 3.x) firmware of ReadyNAS (these were all of the ReadyNAS Sparc units, that used SPARC processors).
* X-RAID 2 is used in ReadyNAS RAIDiator 4.2.x & 5.x and OS 6.
* X-RAID 1 uses a proprietary RAID solution which is a like to RAID 4 type of behavior - therefore the RAID 5 mathematics work out for it in here
Side note: RAID 4 and RAID 5 storage space calculations mathematically work out to be the same.
On top of X-RAID 1 sits the EXT filesystem.
* X-RAID 2 is a genius installation of MDADM on top of carefully carved out partitions, on to which a volume manager is installed.
The volume manager for 4.2.x and 5.3.x is LVM. On top of the LVM goes the EXT filesystem. For 6.x the volume manager and filesystem are combined because BTRFS can handle it all very well.
Note 7b:
Quick note on X-RAID 1 (Only Applies to ReadyNAS)
- This might be incorrect so I will see if I can get this looked over and fix it up if needs be
* The expansion logic with X-RAID 1 is different than X-RAID 2. X RAID 2 does its best to expand on the fly with every new drive.
* HOWEVER X-RAID 1 needs a whole set of new (and bigger) sized drives to expand.
* For X-RAID 1 - there are no longer units available that support this, all the X-RAID 1 units are End of Life.
* With X-RAID 1 The idea is you need to replace all of the smaller drives to utilize the full disk usage
* The X-RAID 1 disk space equation is simple, however its biggest downside is pretty apparent (back in the days of X-RAID 1 however this remarkable):
* The equation for Total Disk Space(not including Overhead) for X-RAID 1 is: (smallest disk in array)*(number of drives-1)=Total Disk Space
* For example an array of 80GB, 80GB, 80Gb, 160GB, 160GB, 160GB would have a total storage of (80 GB) * (6-1) = 80 * 5 = 400 GB
From that 400GB don't forget to subtract the overhead, can't tell you off the top of my head, but it's not much.
However this is a close order of magnitude estimation
Also There was never an X-RAID 1 device with this many drive slots as far as I am aware, the most slots available for an X-RAID 1 system was 4 slots.
Special Thanks goes out to:
NETGEAR KB - Chirpas Article
Read this if confused on base 2 and base 10 disk drive sizes:
Why Your Hard Drive Shows Less Space Than Advertised
###############
--CHANGE LOG:--
###############
X-RAID VOLUME CALCULATOR 1.0 to 1.5 - 9/24/2013:
Made it look better, added some minor calculation fixes (+ or - 1%) to match closer to real ReadyNAS values. Added some important notes.
X-RAID VOLUME CALCULATOR 1.6 - 3/19/2013:
Fixed RAID 6 calculation to only work with 4 members. Before the assumption was RAID 6 works with 3 members (based on logic: RAID 5 works with only 2)
X-RAID VOLUME CALCULATOR 1.7 - 8/10/2013:
Updated for ReadyNAS 6.x stuff, code stays the same, just added notes
X-RAID VOLUME CALCULATOR 1.8 - 1/29/2014:
Moved to ram.kossboss.com
X-RAID VOLUME CALCULATOR 1.9 - 5/9/2014:
More notes at top, and changed base 2 units to TiB and GiB syntax - added Unused and Parity Calc
X-RAID VOLUME CALCULATOR 1.91 - 11/19/2014:
Cant log geoip anymore as that is now a paid service, which I dont want to pay for (will look for free service)
X-RAID VOLUME CALCULATOR 2.01 - 12/08/2014:
Adding more drives (up to 60 or more), also giving ReadyDATA functionality (with vdevs)
X-RAID VOLUME CALCULATOR 2.02 - 12/10/2014:
Changed default font from Consolas to nothing (the system default)
X-RAID VOLUME CALCULATOR 2.03 - 12/10/2014:
Added more information about limitations
X-RAID VOLUME CALCULATOR 2.04 - 12/23/2014:
Added more information about Step 3 and added Go to Domain Link
X-RAID VOLUME CALCULATOR 2.05 - 12/24/2014:
Added Visitor Info
X-RAID VOLUME CALCULATOR 2.06 - 12/25/2014:
Fixed link
X-RAID VOLUME CALCULATOR 2.07 - 12/25/2014:
Fixed Text
X-RAID VOLUME CALCULATOR 2.08 - 02/22/2018:
Fixed Changelog newlines
X-RAID VOLUME CALCULATOR 2.09 - 02/25/2019:
Changed from kossboss.com domain to infotinks.com domain
X-RAID VOLUME CALCULATOR 2.10 - 12/15/2021:
Fixed Changelog newlines. Fixed "vers" variable type from float to string.
X-RAID VOLUME CALCULATOR 2.11 - 03/19/2022:
Added information about btrfs storage calculator that has similiar mechanics to xraid.
###############
--VISTOR INFO:--
###############
24 hour visit bar chart (by
revolvermaps.com
)
Visitor globe (by
revolvermaps.com
)