Raising the roof on the shingled write problem

Read and write track width asymmetry

Internet Security Threat Report 2014

Shingled writing has a serious problem: writes take more time than current disk writes, probably ruling out enterprise use unless complex flash memory technology is used.

The problem stems from the layout of heavily overlapped tracks in shingled write recording (SWR) and the direction of writes. Together they mean that a random, in-place replacement of data on a single track cannot be done without rewriting the data on adjacent (overlapped) tracks as well, and this takes time, a lot of time in disk access terms.

As perpendicular magnetic recording (PMR) heads towards 1Tbit/in2 and the looming supraparamagnetic limit and world of randomly changing magnetic states the two main successor technologies, BPM (Bit-Patterned Media) and HAMR (Heat-Assisted Magnetic Recording), plus the third and theoretical alternative, MAMR (Microwave-Assisted Magnetic Recording), all pose intensive, complex and very costly development and production challenges. Thus the HDD industry is suffering a collective bout of pre-production financial indigestion and searching for a common way forward via the Storage Technology Alliance (STA).

SWR has been proposed as an interim way forward - one that could be applied to current PMR media and extend its life towards 2-5Tbit/in2. Use of 2D readback and signal-processing could extend it again, such that the combination of this and SWR in Two Dimensional Magnetic Recording (TDMR) could perhaps attain 10Tbit/in2.

(This information comes from an IEEE Transactions on Magnetics, Vol. 45, No. 10. October 2009, and an article entitled "Future Options on HDD Storage", which is only available behind an IEEE paywall. In our view such papers should be openly available and free of charge. It is a disgrace that they are not. )

Overlaid tracks

In SWR a hard disk drive gets more tracks because each track except the innermost ones are overlaid by the next track. The picture shows this effect, with each resulting track having only about a third or less of its width along one edge not overlapped by the adjacent track. The result is much narrower tracks.

The authors of the paper say: "Readback (with a suitably narrow reader) is unconstrained and random-access reads work just as in a conventional drive … Reading a sector from a shingled written surface may have conventional performance."

Shingled writing

Shingled disk writing diagram.

The next sentence reveals the problem: "A huge disadvantage is that 'update-in-place' is no longer possible."

What do the authors mean? They write: "Tracks are written sequentially in one direction cross-track. Therefore, a single track or portion of a track cannot be altered without first recovering many tracks of subsequently written data."

It's obvious, isn't it? If you replace and re-write the data already on a track A, which has 75 per cent or more of its width overlaid by two or three other tracks (B and C), then a write to part of track A obliterates the data on the overlapping parts of tracks B and C as well, because you write in the full track width while reading in the narrow track width. This asymmetry is the issue.

What the shingled HDD has to do is to first copy the data that is going to be overwritten into some buffer, taking let's say three disk track accesses, write the new data over the old data in the buffer, copy the bugler data, and then rewrite the data back onto all the tracks involved on the disk surface, taking another three disk track accesses. So we have six disk track accesses and three buffer data operations, taking a much longer time than the single track access needed in today's PMR, non-shingled drives.

Put it another way; will enterprises buy shingled HDDs if rewriting data takes seven or eight times longer than with today's drives? Of course they won't. SWR drives won't find a place in applications where fast write I/O is a requirement. Some commentators think the only place they will find an application is inside the slow write world of personal video recorders (PVRs).

What can be done to fix this? The authors of the paper suggest adding in two-dimensional readback and signal processing technology, and using firmware techniques such as those needed to overcome the block erase-write cycle delays in solid state drives.


The authors state: "For 2-D readback, powerful signal processing can be applied that takes advantage of knowing the waveforms on the adjacent tracks. A highly accurate track following system will also be applied to deliver the required spatial resolution."

As well as: "By applying firmware similar to [the SSD firmware above] TDMR should be able to offer a standard HDD interface supporting small random writes and deliver write performance comparable to today's HDD by dynamically remapping written sectors to append to the most convenient band of shingles. If multiple adjacent tracks must be read to recover a sector, very effective buffer caching will be needed to mask the large latency of such reads."

In more detail TDMR needs readback signals to be available from several adjacent tracks so that a 2-dimensional waveform or image can be constructed. This waveform has powerful 2-D coding and signal-processing applied to it and this takes account of, if not advantage of, inter-track interference. Gaining the information from adjacent tracks means a multi-track reader or progressive scans with a single head, meaning extra time will be needed for the extra three to five disk rotations involved. A lot of research is needed to see if this approach is viable.

If this approach is used then additional system memory will be needed, meaning extra cost, and more cost still will come from using a full 2-D readback process.

It's apparent that although shingling is less expensive to develop than BPM or HAMR, it is not an easy option. But shingling and full TDMR can be applied to both BPM and HAMR media as well as the current media, so once suppliers know how to do it they can continue using the technology. ®

Top 5 reasons to deploy VMware with Tegile

More from The Register

next story
Docker's app containers are coming to Windows Server, says Microsoft
MS chases app deployment speeds already enjoyed by Linux devs
'Hmm, why CAN'T I run a water pipe through that rack of media servers?'
Leaving Las Vegas for Armenia kludging and Dubai dune bashing
SDI wars: WTF is software defined infrastructure?
This time we play for ALL the marbles
'Urika': Cray unveils new 1,500-core big data crunching monster
6TB of DRAM, 38TB of SSD flash and 120TB of disk storage
Facebook slurps 'paste sites' for STOLEN passwords, sprinkles on hash and salt
Zuck's ad empire DOESN'T see details in plain text. Phew!
Windows 10: Forget Cloudobile, put Security and Privacy First
But - dammit - It would be insane to say 'don't collect, because NSA'
Oracle hires former SAP exec for cloudy push
'We know Larry said cloud was gibberish, and insane, and idiotic, but...'
Symantec backs out of Backup Exec: Plans to can appliance in Jan
Will still provide support to existing customers
prev story


Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Win a year’s supply of chocolate
There is no techie angle to this competition so we're not going to pretend there is, but everyone loves chocolate so who cares.
Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Saudi Petroleum chooses Tegile storage solution
A storage solution that addresses company growth and performance for business-critical applications of caseware archive and search along with other key operational systems.