jcampaz516 wrote:
Hi Mes. Yes, best practice is to make 'skinny LUNs' and untick Space Reservation off the LUN. As mentioned before, the Windows OS will not see the benefits but the parent volume will as the blocks will be visible/accessible at this level making it possible for your other LUNs in the same Vol to have access to these free blocks. This is what we are doing in our set up. The best practice doc should be arriving soon, TR3702 version 3. They are almost done with it. Hope this helps. Ping me back if you have any other questions.
- Jeff
Jeff,
When you make skinny LUNS and untick space reservations, where are the free blocks go to? You say they will be available to the volume, but the tr doc says they will be available to the aggr.
Could you explain this? If they are going to the aggragate i would create another CSV for hyper-V in that aggregate. Otherwise i would create or expand the csv LUN in that volume.
Tomas