Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

4/6/2010
12:15 PM
George Crump
George Crump
Commentary
50%
50%

What Is Zero Detect?

There is a term you are going to start hearing more of in storage circles; Zero Detect. Some storage systems that offer thin provisioning are adding the ability to detect areas of a volume that have been zeroed out so they can reclaim that space and use it elsewhere. Zero detect becomes a critical component as we advance the capabilities of thin provisioning.

There is a term you are going to start hearing more of in storage circles; Zero Detect. Some storage systems that offer thin provisioning are adding the ability to detect areas of a volume that have been zeroed out so they can reclaim that space and use it elsewhere. Zero detect becomes a critical component as we advance the capabilities of thin provisioning.Most file systems when they are told to delete a file, simply mark the area as available to be overwritten, they don't actually remove anything. This creates a challenge for storage systems that offer thin provisioning. If you delete a large amount of data to free up capacity, the thin provisioning system will not be able to understand what happened and reclaim that capacity. The result is that overtime thin provisioned systems used to "gain weight" as files were deleted from the file system. In other words the thinly provisioned volumes most efficient day was its first.

Despite this shortcoming, thin provisioning has caught on, almost becoming a required feature. The ability to only allocate capacity as it was needed, even if you could not later reclaim that capacity, still saves many organizations lots of wasted capacity. The ideal situation is to be able to reclaim the deleted space as well and the next era of thin provisioning will be defined by vendors that can advance the state of the art to address this challenge.

Which brings us to zero detect. As I said earlier a file system does not automatically zero out deleted blocks. It just marks them available to be overwritten. A separate utility will have to be run that will scan the file system for deleted files and then zero them out. Once thats done the zero detect aware thin provisioning system can scan the volume and identify the blocks that have been zero'ed out and reclaim those areas. While this adds a few extra tasks to the storage administrator's todo list, imagine being able to reclaim TB's of capacity. This will likely become a housekeeping chore that is run once a week or month but the return could be well worth the investment in time.

Zero detect does let a few worms sneak out of the can though. There will be issues with how many consecutive blocks of deletion are available before the space can be reclaimed and all of this scanning is going to take processing power on both the attached server and especially on the storage system. Storage system suppliers will have to come up with ways to address at least the later.

The ideal solution may be to have a file system that is thin aware and communicates directly with the storage systems. This would allow the storage systems to reclaim the space as soon as it becomes available. The communication would eliminate the need for a separate maintenance process as well as reduce the impact on server and storage processors.

There is an effort within the Technical Committee T11, which is the committee within INCITS to produce a standard interface between file systems and thin provisioned storage systems. Until this standard becomes ratified and established it is going to be on the file system vendors and storage hardware vendors to work together. Until that time though the zero detect method may be the only way to enable thin reclamation.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Avi_123
100%
0%
Avi_123,
User Rank: Apprentice
4/12/2015 | 7:07:42 AM
Thanks
Very useful post George.

Cheers

Avi
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.