But if i deleted ~ 100GB data and i also deleted 100GB of reclaimable snapshot space shouldn't some of that have gotten picked back up in the actual volume? that doesn't make sense that none of it gets reclaimed. it's highly unlikely the 100GB of data was using was deduplicated 100%
Not likely they were sparse files since a bunch of it was assets like jpg files html files etc etc. there were also a couple databases which those possibly could've been but i still would've expected like at least 20% return of space.
And no i haven't seen the space change since doing a df again
They could be held in the snapshot space. If you delete the snapshot it takes time to complete the delete, it's considered a background task, check back in a few hours (depending what else is going on).
aborzenkov is correct - I understood your OP to say that you deleted about 100G from the filesystem, THEN deleted the snapshots - but if you just deleted 100G in snapshots, the live filesystem space won't reflect any change, and in that case you should have seen the snapshot space go from 100% to 0%.
So it should've been approximately 100GB of data I was trying to reclaim on the filesystem by doing an rm –fr on an nfs mount
My assumption is by doing so that shoves it all into the snapshot
So then I deleted the snapshots which said the reclaimable was 80 some odd gigs.
I did notice the snapshot used went from pretty full down to 0 , which I kind of expected but I was also expecting some of the regular volume to get something back. And by something I mean like more than 0
Anyhow I'm pretty much done chasing down space so I'm just going to work around this by shifting some data or reducing my snapshot reserve as mentioned before.
You have a volume with 921GB of data space and 102GB of snap reserve space. So you have a 1TB volume using 10% snap reserve.
You had 100GB of snapshots.
Those snapshots fit neatly into the 102GB snap reserve.
You deleted said 100GB of snapshots and didn't see the usable data space change.
The thing is, when you made the volume and set aside 10% for snap reserve, it removed that amount from your usable data space and reserved it just for snapshots. Think of it as stowing stuff below the floor tiles in the data center. The room is actually bigger than you see but you raised the floor so you could have a place to keep power cables and such. I can add and remove power cables all day just as long as I don't try to stuff more cables down there than I have crawl space. At that point, the cables would poke up through the floor tiles and start taking up space in the data center, lessening the amount of work space that I had. At that point, I could remove some of the cables and reclaim my old amount of work space in the data center.
Same thing with the snapshots. Snapshots will fill up snap reserved space first. If they run out of snap reserve space, they will start taking up data space and count against your % available. This wasn't the case with you as all the snapshots were still within the snap reserve. If you want to recover some data space, you will have to reduce the snap reserve from 10% to something lower, which will apply the difference to your % available. Keep in mind that you will still be writing snapshots. If you want to lower your snap reserve, you will need to adjust your snapshot retention requirements or you will have snapshots exceeding your snap reserve pretty quickly. Basically, you just lessened the amount of crawl space below the floor tiles in your data center but you still need to leave some space for necessary cables.
To free space you need to delete all snapshots that keep "copy" of deleted file(s). Whether it happens "next time snapshot schedule runs" depends on which snapshots have these files and whether these snapshots are deleted when "snapshot schedule runs".