NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Anybody know how big a volume I can create with Radiator 4.2.31?
I've got these Western Digital 6TB gold drives (please see attached file). Here's the thing. If I let the ReadyNas 2100 create an X-Raid2 volume it uses up all of the space, and then it says the ...
Thanks everybody for your advice.
The final number: 16,273,912 MB is what you would put in. That's including "10 GB" for snapshots, although I think the software is in error, I think that really means "10 %" for snapshots.
(If you put 16,273,913 MB that is the smallest size that is too big to be created into a successful volume.)
For ReadyNas 2100 v1 running Raidiator 4.2.31.
Raidiator 4.2.x uses mdadm and LVM for creation of volumes. Everything I have found says LVM is limited to "16TB" on a 32-bit Linux installation. Now, since that's based on the bus width, I assume they actually mean 16TiB, which you are under. But perhaps there is something in the Netgear Frontview portion that causes the issue.
When you say "I can't do anything with it. No error state, just inaccessible", does that mean you tried to actually put files into that "full" volume and it failed (after completion of sync)?
Do you have SSH enabled? If so, what do you get from the following commands?
cat /proc/mdstat
lvdisplay
pvdisplay
vgdisplay
The best way to put the results into a message is to use the insert code </> icon at the top of the editor.
Thanks everybody for your advice.
The final number: 16,273,912 MB is what you would put in. That's including "10 GB" for snapshots, although I think the software is in error, I think that really means "10 %" for snapshots.
(If you put 16,273,913 MB that is the smallest size that is too big to be created into a successful volume.)
For ReadyNas 2100 v1 running Raidiator 4.2.31.
It's also worth noting that you can have multiple volumes and I think from memory any disk can be in up to two of those volumes.
It would still be interresting to see the results of those commands to see what's causing that limit. My only 4.2.31 system is a Pro2 with two 1TB drives, which I use as a "sandbox", so not remotely comparable to what you've created, but vgdisplay returns the following:
Pro2D:~# vgdisplay --- Volume group --- VG Name c System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 1 Act PV 1 VG Size 927.00 GB PE Size 64.00 MB Total PE 14832 Alloc PE / Size 14672 / 917.00 GB Free PE / Size 160 / 10.00 GB VG UUID RqY3q9-Wtgu-WP2I-znww-LNJZ-lXDM-7mNL8n
And I've assumed that the 10.00GB Free PE is the snapshot reservation. To make a 16TB volume, the PE size is going to have to be bigger than 64MB, so that may be a part of the equation. I suspect that's also tied to the reason for the expansion limits. XRAID has to choose an appropriate PE size when you create a volume, and that can't be changed. So it chooses one that works well for the current size and gives some expansion capability.
Sandshark wrote:
It would still be interresting to see the results of those commands to see what's causing that limit.
One reason for the inability to expand over 16 TiB is the inode size. The system uses 32 bit inodes if the initial volume is < 16 TiB, and that can't be safely changed later (at least in the ext software in the 4.2.x ReadyNAS). You need 64 bit inodes if the volume is > 16 TiB.
But in this case (4x6TB drives), the system should have chosen 64 bit inodes.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
