• Skip to main content
  • Skip to primary sidebar
  • Home
  • About
    • Stephen Foskett
      • My Publications
        • Urban Forms in Suburbia: The Rise of the Edge City
      • Storage Magazine Columns
      • Whitepapers
      • Multimedia
      • Speaking Engagements
    • Services
    • Disclosures
  • Categories
    • Apple
    • Ask a Pack Rat
    • Computer History
    • Deals
    • Enterprise storage
    • Events
    • Personal
    • Photography
    • Terabyte home
    • Virtual Storage
  • Guides
    • The iPhone Exchange ActiveSync Guide
      • The iPhone Exchange ActiveSync Troubleshooting Guide
    • The iPad Exchange ActiveSync Guide
      • iPad Exchange ActiveSync Troubleshooting Guide
    • Toolbox
      • Power Over Ethernet Calculator
      • EMC Symmetrix WWN Calculator
      • EMC Symmetrix TimeFinder DOS Batch File
    • Linux Logical Volume Manager Walkthrough
  • Calendar

Stephen Foskett, Pack Rat

Understanding the accumulation of data

You are here: Home / Everything / Enterprise storage / De-Allocating is the Core Issue for Thin Provisioning

De-Allocating is the Core Issue for Thin Provisioning

December 29, 2010 By Stephen Leave a Comment

One of the topics I've often written and spoken about is thin provisioning. This series of 11 articles is an edited version of my thin provisioning presentation from Interop New York 2010. I hope you enjoy it!

I began by introducing the core problem: Storage isn’t getting any cheaper, even though raw capacity is cheap. Then I talked about storage utilization and provisioning problems. Now we’re going to talk about thin provisioning.

So, what is thin provisioning? I imagine everybody can just figure it out by the name. It means that instead of allocating storage that we’re not even going to use, we don’t allocate it, and give it to somebody else.

All right. We’re done. Anybody have any questions?

Ok, you caught me. This is actually not how it works. This is how you would like it to work, but this is not how it works. This is the “vendor illustrated” version of how it works. So let’s talk about why thin provisioning doesn’t work this way.

Thin provisioning is problematic. What happens is I allocate some space and suddenly I need a lot more. Perhaps I have temporary requirements and suddenly my application is spitting out log files like crazy, filling up all my storage, and locking everybody out. Oops, that’s a problem. But it’s probably exaggerated by thin provisioning opponents.

One of the biggest technical issues for thin provisioning is not the provisioning part: It’s fairly easy for a storage array to allocate on request:

  1. Operating system: “I need a block; here’s some data I want you to write.”
  2. Storage array: “I’ll just start allocating now.”
  3. But, the operating system never goes back and says “I don’t need that block anymore.”

De-allocating (de-provisioning) is the challenge of thin provisioning. And that’s something that has to be tackled. And the reason that I say that thin provisioning isn’t quite as bad as it used to be is because that problem is being addressed.

Another problem we’re going to talk about is chunk sizes and formatting conflicts. We’re also going to talk about application conflicts.

There are a lot of problems with thin provisioning, but it’s getting better. I’ve been talking about this for years. I actually had a version of this slide that I used in 2003 or 2004, right when 3PAR started really pushing thin provisioning. And at that point I was saying “hold you horses everybody.” Now I’m getting a little more friendly to thin provisioning.

I realized, after years of griping, that my discomfort with so many technologies comes down to this: If people are trying to solve a business problem with a technical solution, they’re going to fail. It doesn’t matter if you’re talking about thin provisioning or anything else.

If your problem is that the organization won’t give you funds to actually buy storage, so you have to steal it from the next project that comes along and then reapply that storage to other projects just to keep your growth up, well, then thin provisioning is not going to solve your problem. If your problem is that you can only buy once a year, or you can only buy when the EMC salesman gives you a super discount and leaves something on the loading dock, well, thin provisioning is not your problem. Your problem is somewhere else.

But if your problem is that you have file systems that don’t like to grow and shrink, or if your problem is that you have a standard size allocation unit that everybody has to use and it always leaves some space empty, you are in luck. These are technical problems and those are things that you can solve with thin provisioning.

I wrote more about this topic in Use Process Solutions For Process Problems, Technical Solutions For Technical Ones

So, just think about it. Are you trying to solve a business problem or a technical problem? And again and again you’ll see that technical solutions should be applied to technical problems and business solutions should be applied to business problems. And there’s no solution to political problems, so what can you do?

You might also want to read these other posts...

  • Electric Car Over the Internet: My Experience Buying…
  • Liberate Wi-Fi Smart Bulbs and Switches with Tasmota!
  • GPS Time Rollover Failures Keep Happening (But…
  • What You See and What You Get When You Follow Me
  • Powering Rabbits: The Mean Well LRS-350-12 Power Supply

Filed Under: Enterprise storage, Gestalt IT Tagged With: allocation, business case, EMC, Filesystems, thin provisioning, Thin Reclamation

Primary Sidebar

A man provided with paper, pencil, and rubber, and subject to strict discipline, is in effect a universal machine.

Alan Turing

Subscribe via Email

Subscribe via email and you will receive my latest blog posts in your inbox. No ads or spam, just the same great content you find on my site!
 New posts (daily)
 Where's Stephen? (weekly)

Download My Book


Download my free e-book:
Essential Enterprise Storage Concepts!

Recent Posts

Electric Car Over the Internet: My Experience Buying From Vroom

November 28, 2020

Powering Rabbits: The Mean Well LRS-350-12 Power Supply

October 18, 2020

Tortoise or Hare? Nvidia Jetson TK1

September 22, 2020

Running Rabbits: More About My Cloud NUCs

September 21, 2020

Introducing Rabbit: I Bought a Cloud!

September 10, 2020

Remove ROM To Use LSI SAS Cards in HPE Servers

August 23, 2020

Test Your Wi-Fi with iPerf for iOS

July 9, 2020

Liberate Wi-Fi Smart Bulbs and Switches with Tasmota!

May 29, 2020

What You See and What You Get When You Follow Me

May 28, 2019

GPS Time Rollover Failures Keep Happening (But They’re Almost Done)

April 6, 2019

Symbolic Links

    Featured Posts

    Not All 802.11n Networks Are Alike

    July 2, 2011

    The Ideal pfSense Platform: Netgate RCC-VE 2440

    September 21, 2015

    What More Could Alan Turing Have Accomplished?

    October 7, 2012

    Scaling Storage At The Client

    November 25, 2013

    The Terrifying True Story Of Virtual Machine Mobility

    December 22, 2011

    How Smart Is the Mondaine Helvetica Smart Watch?

    December 30, 2015

    Why I Am Biased Against FCoE

    October 21, 2011

    The Prime Directive of Storage: Do Not Lose Data

    December 12, 2014

    VMware’s Hardware Partner Strategy: Heads I Win, Tales You Lose

    February 11, 2013

    Scaling Storage In Conventional Arrays

    November 19, 2013

    Copyright © 2021 · Log in