You have either 10 or 11 TB now, depending on whether you are running single or dual redundancy.
After the upgrade you'd have either 14 or 15 TB (again depending on the redundancy you've chosen).
So you shouldn't hit the 16 TB limit.
However there is a second limit - which is that you can't expand more than 8 TB from your starting point. In order to know if that limit applies you'd need to know the number of disks in your initial install (or the most recent factory default)
Take a look at the XRAID Volume Size Calculator (see link in my sig).
Most likely your volume would be configured using X-RAID2 dual-redundancy (uses RAID-6). Even if not (using single-redundancy certainly wouldn't be recommended with this config) you still wouldn't hit that 16TB limit.
Also note there's an 8TB limit for online volume expansion over the life of the volume. Did you start out with all 12x1TB disks installed? If so you wouldn't hit that limit either.
After the upgrade you'd have either 14 or 15 TB (again depending on the redundancy you've chosen).
oops- the correct answer for single redundancy is 16 TB. This doesn't change the overall response though - you still won't exceed the 16 TB threshold, but might exceed the 8 TB growth limit.
Note that these are approximate, and in 1000 byte units, not the 1024 byte units used by frontview and most PCs. The calculator will be more accurate.
Is there any way to tell what the original volume size was? I am not certain which drives I put in originally. I'm concerned that if I replace too many more drives with larger ones I'll end up over the 8TB expansion limit.
There is nothing in the logs that restates what the original size of the volume was when you first factory defaulted. I usually keep track of the sizes in a notepad or something and save it for later reference. There are rotated logs, but they dont go back far enough as the OS only has 4 GB of space so as to maximize the size of the disks. Anyhow if you did start with 12 disks 1 tb each. In ssh mode - becareful not to delete anything - go into /var/log and /var/log/frontview and check out the files, the dated files especially. I doubt they go back far enough to your factory default date, your factory default date is recorded in initrd.log in /var/log/frontview.
I poked around on this myself on my Pro-6, and didn't see anything obvious. Somehow the system knows (otherwise expansion wouldn't fail when the limit was reached), but I didn't see any clear indications when I looked at the file system details.
I poked around on this myself on my Pro-6, and didn't see anything obvious. Somehow the system knows (otherwise expansion wouldn't fail when the limit was reached), but I didn't see any clear indications when I looked at the file system details.
Yes, this was my thought too. There has to be something other than the logs to record the original size. It can't just fail from "The Great Mysterious Curse of Expansion", an insidious rite performed upon initialisation, one that only the Gods are privy to!
I found the logs as part of the download logs, 'expansion.log'. It showed I had 4 x 1.5TB drives installed on initialisation so, in theory, I should be able to expand to 12.5TB. However, I have just replaced the 2nd to last of the 1.5TB drives so that I have 5 x 3TB and I'm now hitting a "Volume Expansion Failed" error.
