No, I’ve discovered a little more info. It seems that the units have different disks, and they format to different sizes.
This translates to being able to build a 112 disk aggregate on one unit, but not the other, due to the difference
in the formatted size (I think, yet to confirm by doing the maths manually). So, I _do_not_ have an aggregate over 
the 70TB size limit, I just have different operable disk sizes. 
I’m actually quite relieved by this discovery, as for a short while, I thought I’d managed to get a 3170 outside of
it’s normal operating parameters, but it turns out not :)  I’m just not that good at maths.

`Mark

 
On 5 May 2016, at 13:53, Brad Thompson <brad.thompson877@gmail.com> wrote:

Honestly, I'm a little more interested in the controller that let you build an aggr over 70TB.  According to the HWU, the max aggr size for a FAS3170 running 8.0.5 is 70TB. 

Maybe this is a dumb question, but are you sure they are both running 8.0.5P1?  It looks like the max aggr size was increased in 8.1, and then again in 8.2.

On Thu, May 5, 2016 at 5:19 AM, Mark Flint <mf1@sanger.ac.uk> wrote:
Hi all. I have 2 x FAS3170’s, both now running 8.0.5P1. On one unit, I can build an aggregate of over 70TB, 
yet on the other, it won’t allow this to happen. Both aggr’s were built using the CLI :-

aggr create aggrgate1 –B 64 –r 16 –t raid_dp 112 ( 96 )

the 96 is the aggr built on the unit that is restricting aggr size. 

Anybody seen this before, or have any ideas?

Thanks,

`Mark 

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters