Question about hard drive structure...

I was just reading something about how hard drives store information.
Apparently, data is stored by magnetizing a series of concentric circles called tracks. Each track is track is divided into a number of equal sized wedge-shaped regions called sectors. Each sector, throughout the disc holds the same amount of data, usually 512 bytes.
So you can imagine a disc, with a bunch of rings, and a bunch of lines radiating from the center to divide the rings into sectors.
The thing that gets me is, in order to have each sector hold the same amount of data, the bytes have to be more closely packed together in the center than at the edge!?:dubious:
Would it not be better to maximize the storage capacity by packing them just as close throughout the disc and increasing the sector size as you get closer to the edge?
Or is it so much easier to process the data if each sector is the same size that storage efficiency takes a back seat?

Storing gobs of data is fine, but it’s also important to be able to access the data at a consistent speed.

http://www.ntfs.com/hard-disk-basics.htm

This used to be how disk drives were built. But not for quite some time. As noted above such a design makes the control electronics a lot easier to build - since all the timing is the same. Modern drives will record a constant data density and vary the timing to compensate. However this makes the control systems much messier, and disks much harder to describe. You still have tracks, but a varying number of sectors per track. There is a fiction maintained about sectors per track. Older file systems and disk controllers had the old idea of disk layout built into them. So you may find yourself having to fabricate a disk geometry specification. This usually ends up with the real number of tracks, and a number of sectors per track that results in a capacity that is correct for the disk. But it remains a fiction.

Ok, I never considered the consistent speed issue. Makes more sense to me now. Thanks :slight_smile:

Francis, are you saying that modern drives do in fact store data in the same density over the whole disk and just slow down to read the outer tracks?
I think I understand what you mean about the “fiction”. Are you saying that the software expects the old uniformly sized sectors and we come up with specifications describing the disk as it would be if it were the old design so that the software can control the hardware properly? If I have misunderstood, please clarify.

They can’t slow down the disk - but the drive electronics are now sufficiently flexible that they can cope with sychronising to data coming off the disk surface across a reasonably wide (say 2:1) range of data rates. And can also sychronise approriately to write data. You have the idea of the fictional description spot on. However it isn’t so much that the software can control the hardware properly, just that the software feels happy in its little cocoon. Other parts of the operating system will simply turn the specification back in to a linear space of blocks. It used to be that you asked the disk for platter, track, sector. Now you just ask for a block, where block numbers start at zero and run to the end of the disk.

Disk manufactures are remarkably reticent to tell you much about what really goes on inside a disk drive nowadays.

They don’t slow down, they just know the difference between the inner and outer tracks and can read the sectors even though there are more or less sectors per revolution near the edges.

I believe that would be “more”.

I haven’t disected a drive recently, but when I did, the number of sectors was not constant from center to edge. However, the interfacing software was set up to translate from actual to virtual locations and vice-versa so older drivers and opsys could handle it without a serious modification.

And, how could you tell this by dissecting a drive? Can you see magnetic domains?

No. I mean disecting the software. If you have access to a translation table, you can see how the physical is mapped to the virtual.