EVA 3000 disk occupancy alarm

[Dusty Mjoen]

We are running an EVA3000 with version 4007.  We recently replaced a failed drive, and now the disk group occupancy alarm (exeeds 95%) has been activated.

The problem is the windows system that the LUNs are presented to does not agree with this.  According to the drive on Windows there is over 2TB available, while CV reports ony 72GB.

Any ideas what may cause this?

[Torsten. · Accepted solution]

Sometimes the controllers report wrong space information. You could try to reboot the EVA controllers one by one first.

Did you group the exchanged disk?

[Dusty Mjoen]

I think you are on to something.  It appears we have not been grouping our replaced disks.  We currently have 3 disks in an ungrouped state, including the one we recently replaced.  It appears I can regroup them on the fly?  Would it be best to phase the three of them back in?

Thanks!

[Torsten.]

Just select the appropriate diskgroup and group them all in a single step, if possible.