This may occur if you have your space guarantee on your volume set to "volume", but not enough space in the aggregate to accommodate the full volume size. Space and fractional reserve can play into this too. Can you post the results of the following commands?
aggr status show space -g
vol status -v
snap reserve -V (CAPITAL V)
This should help us determine if this is the case exactly. If all you did was replace a HDD of the same size then I'm not sure offhand why this would happen. WHen your previous HDD went bad your hot spare should have replaced it automatically (assuming you had one) and nothing should have changed size-wise.
The only concern I have is that you *should* be able to use a volume guarantee on this volume given the space you have available and I'm wondering why it's not allowing it. You probably should not leave the guarantee at none or you may run into issues down the road if the volume grows.
Please rerun the commands I gave you above and report the output once the vol_cifs is online. Unfortunately, I can't see the options I need to when it's offline.
This means they have thin-provisioned the volume, and the containing aggr now does not have enough space to meet the garantee to volume. So it offlines the vol as a way of protecting the data.
Consider a scenario where you have a 100 GB aggr, If you thin provision, you could have (3) 50 GB volumes with no space guarantee online at the same time. Great! Make it appear to the users like you have space, add the disks to actually have the space later.
However, if you set the space garantee to "volume" you have to have all that space available NOW as a way of protecting that data. If you can't guarantee that space, you will see the error you got. It simply will not online the volume.