Linked by moondevil on Wed 11th Jan 2012 00:10 UTC
Permalink for comment 502806
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2006-06-09
Well, overcommit is possible but is a pretty niche feature for big old stupid DBs in server environments where you're better announcing a giant data partition and letting it be initialized at once rather than bring it down for maintenance every time to expand it later.
The more important feature of thin provisioning is that pool space is allocated on the fly to the individual volume requesting it.
Basically, on a 1TB drive you're going to have C: D: E: volumes each reporting 1TB available with their free space shared and you wouldn't need to worry about running of space or wasting it on some volumes. But you will still have 1TB in total, of course. And I'm not sure if Windows will be able to reclaim and reallocate unused space.
It certainly won't panic. Ever tried to add a swap file with holes in Linux? It simply won't allow this. You have to allocate every 0 of it to a real storage.