Subscribe

No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

[ Edited ]

Initially I got errors (0xc00408d3, 0xc00402c2, and 0x00402206) during a daily snapshot on SQL database through SnapManger for SQL. I called NetApp for support many times but not much help. It's been 3 weeks from the initial call. I really need help to get this issue solved. I deleted all backups through SnapManager for SQL. I don't see any changes in volume available size. I also deleted some snapshots through filerview. I still didn't see any changes in volume available size.

What have I not done right?

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

I have had this problem before and had to grow the volume in order for it to sort it's self out. Once it is running again to can shrink it back. {Flexvol assumed} The problem is with how LUNs use reserve. The snaps go into the volumes data space 1st then fill up the reserve space.

If you connect to the consol you can use the command

df -V -g

To view all the volumes on the filer and how the space {in Gb} is used. Use the command

df -A -g

To see how much space you have in the aggregates. Once aggregates are above 80% full you are heading for pain but thats another story...

vol size {volname} +5g

Will grow the volume by 5 Gb

vol size -5g

Will shrink it back by 5 Gb

Good luck

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

Are you saying that I have to increase the Volume for it to clean up (shrink) itself back? I'm new to NetApp SAN. I just increased the volume by 10 GB. How long will it take to shrink itself back? How do I know that increasing by 10 GB is enough or not?

Thanks,

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

This can happen in two scenarios that I have seen thus far:

  1. Deletions sometimes take some time to complete on heavily utilized systems.
  2. If the aggregate is already over-committed, there is no space to give back.

The latter seems to be the most probable. To confirm this theory, try these two commands:

  1. "aggr show_space"
  2. "vol status -v" and look for "guarantee"

In the "aggr" command, the output is self explanatory. In the latter, if you see ANY volume that has guarantee set to "none", in essence, that is a volume that has the ability to be sized above and beyond the physical confines of the aggregate.

Please confirm.

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

All volume status show "guarantee"

volume=guarantee.

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

I increased the volume by 10GB. Now I can make a snapshot without any error. I deleted about 2/3 of all snapshots. It's been over 5 hours, but the volume consumpsion has not reduced.

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

What version of ONTAP? Do the numbers in "aggr show_space" look as expected?

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

I think the version is 7.2.4L1. I'm expecting the log (the trouble volume) consuming less space since I deleted about 2/3 of snapshots within the volume. It's been over 5 hours, but the volume consumpsion has not reduced. I also increased the volume by 10GB. Now I can make a snapshot without any error. I don't see any changes in the volume consumpsion.

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

Check space reservations on your luns. If you have space reservations enabled, the luns will require twice their size in the volume for lun snapshots. There is a whole section on space reservations in the ONTAP documentation which will do you more justice than I can do in this little box ;-)

Here's a link with respect to your ONTAP release:

http://now.netapp.com/NOW/knowledge/docs/ontap/rel724L1/html/ontap/bsag/4cr-f3.htm

The command "lun show -v"will tell you if space reservation is enabled on your luns.

Let me know if this seems like the issue; I'm now suspecting it is.

Re: No space available left on a volume. After deleting some snapshots through filerview and backup through SnapManager for SQL, I didn't see any changes in volume available size.

Yes. the space reservation is enabled on all luns. Is that the best practice? The SAN was implemented by one of the well-known Boston consulting firm. I also was highly suggested to stay with these settings. I'm very new to NetApp SAN. I got the Snapshot to work by increase the size of the volume. I also deleted both SQL backups and Snapshots. I don't see any increase in available volume space. It's been a week since I deleted those. How do I reclaim the space after deleting the snapshots?