Sorry, one further question as we are far from experts. We have had a look on the compatibility site and our current disk firmware is A02 and the required for the new disks is A05 so we will need the disk qualification package. The question is, could the package cause the A02 firmware disks to update automatically and is there any risk to this operation (e.g. data loss)? We will obviously back up the data first but would like to know the possibility of things going wrong.
We have managed to add the disks and change the ownership. It did give a label error which is to be expected which we fixed with an unfail command, it updated the firmware on the disks and we zeroed the spares and added them into the aggregate.
Final question if you please?
The best practice now dictates that we should run a reallocate on all the volumes (not the aggregate) for all volumes on this aggregate but there seem to be many threads advising not to do this on a snapshot enabled, deduplicated volume aggregate. The articles did all seem to point to version 7, where we are on 8.2. Is this still an issue/are we safe to run a reallocation on these volumes?
Thanks very much for any responses, your help is very, very much appreciated!
For completion, here is the eventual response I recieved,
"After we have compared the autosupports from before and after the expansion:
- /aggr0/plex0/rg0 expanded from 11 to 15 disks
- volumes do not have space guarantee,
- used data on volumes has gone down as well.
it turns out that right now there would be no immediate need to use reallocation as there would be (1) enough space on disks themselves and (2) enough disks have been added to the raid group to avoid 'hot disk'.
The only scenario when you would need reallocation is when there are performance issues due to deleting large amount of data (causing large fragmentation). If such a problem ever occurs in the future, please open a performance issue (Cat 1 - Performance) and we will assist you accordingly."