That's craptastic given the amount of upgrades that are performed.

However, given the way the reallocate works, I'd surmise that if you run the command on the flexvol layer (or the LUN/File layer) that performance would be better for those files. The aggregate (as a whole) should only have problems on new writes, specifically, for new LUNs/volumes, until the space is leveled out.

You could also expand the aggregate (provided that you're not at the limit) to include a new RG of 7 disks. We've been doing this for a while here to prevent ever adding smaller disks: always build at 7+2P or 14+2P so that you only ever add in 7 data disk increments.

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Alexander Schalek Sent: Saturday, December 22, 2007 7:59 AM To: 'Eino Tuominen'; NetApp Toasters List Subject: AW: R200 aggregate reallocation

Solution ID: kb27342

Some aggregates cannot be reallocated

Symptoms Aggregate reallocation command reallocate start -A -o may fail to run on some aggregates and return the error message: Unable to start reallocation scan on <AGGR>. Aggregate created on older version of ONTAP. Some aggregates cannot be reallocated

Cause of this problem Aggregate reallocation ('reallocate -A') cannot be performed on aggregates that were created on Data ONTAP versions prior to 7.2.

Solution 'Reallocate -A' can only run on aggregates that were created on a system running Data ONTAP 7.2 or later.

Not sure but I guess you have to create a new aggregate and copy the data to it

alex

-----Ursprüngliche Nachricht----- Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Eino Tuominen Gesendet: Samstag, 22. Dezember 2007 11:45 An: NetApp Toasters List Betreff: R200 aggregate reallocation

Hi,

I had to add just 2 disk to an existing aggregate. I suspect those disks will end up being a performance bottleneck, so I tried to start reallocation of the aggregate:

toaster> reallocate start -A aggr0 Unable to start reallocation scan on 'aggr0': Aggregate created on older version of ONTAP

What's the best way to proceed?

-- Eino Tuominen

Robert Fair wrote:

If you wish to reallocate existing data to new disks added to an aggregate then this can be done at the volume or file level using the full reallocate mode (-f), e.g 'reallocate start -f /vol/VOLNAME'.

Another dead end:

toaster> reallocate start -f /vol/vaultbackup Unable to start reallocation scan on '/vol/vaultbackup': target has snapshots

It's the main snapvault target volume, so snapshots there are...

Aggregate reallocate coalesces free (unused) space, which is not typically what you want in cases like this.

Ok.