HDD Manufacturers Moving To 4096-Byte Sectors

Luminous Coward writes "As previously discussed on Slashdot, according to AnandTech and The Tech Report, hard disk drive manufacturers are now ready to bump the size of the disk sector from 512 to 4096 bytes, in order to minimize storage lost to ECC and sync. This may not be a smooth transition, because some OSes do not align partitions on 4K boundaries."

Comments

Factors of 10

[suso]

Why not just move it to 1000 byte sectors, then we could minimize the space lost to advertising.

(Note to accuracy nazis, this is meant to be funny)

Re:Factors of 10

[rolfwind]

If they want to use base10 the first thing they should do is respecify a byte to be 10bits.

How about leaving the word byte alone and using another, distinct group of letter to do the job? Respecifying only confuses the issue, even those who know, because you're still be working with two different definitions in the same field for a long time.

Re:Factors of 10

[TheRaven64]

A byte can be 10 bits; it's an architecture-specific quantity. An octet is always 8 bits.

Re:Factors of 10

[drainbramage]

Mine goes to 11.

Re:Factors of 10

[pauljlucas]

How about leaving the word byte alone and using another, distinct group of letter [sic] to do the job?

The original definition of "byte" was the number of bits used to encode a character of text and is the basic memory-addressable element in a computer. It never originally meant "8 bits".

Re:Factors of 10

[m1xram]

That's Grey Code. 000, 001, 011, 010, 110, 111 and the joke should read...

There are only 11 types of old timer geeks... :-)

Re:Factors of 10

[dissy]

Wrong.
A word is architecture specific.
A byte is ALWAYS 8 bits.

A byte can't possibly "always" be 8 bits, when a byte means a single character.
This is the definition of 'byte' from 1959. People only started getting confused recently (Recently being the past 20 years) since the IBM 360 systems which first introduced the 8 bit byte and then became a defacto standard in the 80s. Then as new computer users moved into the front, such as yourself, you assume a byte must be 8 bits because that is all you have seen a byte to mean.

There are systems that encode a single byte with 7, 8, 9, and 10 bits still today.

The only time a byte is 8 bits is when the system is structured around 8 bit units.
Hop on a PDP or Cray system and you will see a byte is 7 or 9 bits respectively.

Origins of the word 'byte':
http://www.trailing-edge.com/~bobbemer/BYTE.HTM

Re:Factors of 10

[macemoneta]

[blockquote]The original definition of "byte" was the number of bits used to encode a character of text and is the basic memory-addressable element in a computer. It never originally meant "8 bits".[/blockquote]

That is the definition of 'octet', a term frequently used in telecom. People confuse byte and octet all the time, because popular hardware architectures use an octet as a byte.

Re:Factors of 10

[NovaHorizon]

*clears throat* ....
WHOOSH

Re:Factors of 10

[the_enigma_1983]

I see four numbers there, representing the decimal numbers 0 through 3 inclusive. He's not saying that "00,01,10,11" are labels for types of people, he's saying the number of types is "11", which if read as a binary number is 3 in decimal.

Re:Factors of 10

[afidel]

Dude, MS's KB for kilo-byte predates the silly KiB definition by about two decades (KiB was only adopted as a standard in 2000 and proposed in 1998, MS DOS traces to M-DOS in 1979). Oh and as to performance, almost nothing writes in 512byte chunks, 4KB chunks are about the smallest defaults for current platforms and 8KB is becoming more common.

Re:Factors of 10

[drsmithy]

It's also worth noting that this is Microsoft's fault. Other OS's are doing it properly. Microsoft only does it properly when it benefits them. HDD manufacturers have faced numerous lawsuits simply because Microsoft is using the wrong prefix, so people feel cheated out of space.

I hate to rain on your anti-Microsoft parade, but back when hard disk manufactures realised they could make their hard disks look bigger than they really were, capacities were still being measured in 10s of MB, and *all* OSes were using power-of-two prefixes.

The rest of your rant is about as accurate.

So only XP is out of luck?

[7o9]

According to the Anandtech article, only the pretty much end-of-life Windows XP is out of luck. Linux, OS X and modern Windows versions all work ... Non news?

Re:So only XP is out of luck?

[gbjbaanb]

whoooooo. WinXP is end-of-life? You'd best tell that to all the millions of users (including big businesses) out there.

What that's you say? Upgrade to Windows 7 and use its perfectly infallible XP mode?

Ah, I understand now. Hi Bill, how's Steve getting on, still a bit sweaty and concerned he's not selling enough?

Re:So only XP is out of luck?

[iamhassi]

"WinXP is end-of-life? You'd best tell that to all the millions of users (including big businesses) out there."

Couldn't agree more. Hopefully I don't have to rehash how horrible Vista was, and Windows 7 came out a few months ago so it's a bit early to proclaim XP is dead when it's hopeful replacement just showed up.

I think 4096-byte sectors are Very Bad News. I have no experience with these drives but XP doesn't like them which is reason enough for me to avoid them. I hope hard drive manufactures come out with a standard naming scheme for these new drives so they're easy to identify online, like IDE, SATA, PATA, etc. Maybe AFD for Advanced Format Drive?

Re:So only XP is out of luck?

[iamhassi]

ah this was what I was looking for: Drobo, XP Users: Beware of 4K “Advanced Format” Drives!

Article states that not only will XP have problems but so will many other devices like media centers, USB drives, game consoles, and anything else that uses a hard drive. USB drives will be the worse though since 4k drives formatted for XP won't work with Windows 7 and vise versa. Honestly I think this is too soon, put it off another 10 years, by then we'll have OS's that would have supported 4k for 10+ yrs already and all devices should be compatible by then.

Re:So only XP is out of luck?

[AlecC]

Why wasn't it done before? Sheer inertia. 512 bytes has been the HDD sector size since time immemorial. Some HDDs in the past could be re-sectored to different sizes, and sometimes were. I did it on one generation of disks to optimise storage for a particular reasons, but it didn't work reliably on the next generation of disks, so I dropped it. Some disks had a sector of 1080 bits, I think to handle the 33rd bit on IBM System/38.

What is the advantage? Every sector has a preamble, a sync mark, a header, the payload data, ECC, and postamble. These can amount to tens of bytes, especially as you have stronger ECC for weaker signals. By having fewer sector, you recover this space from most of the sectors. This could easily add 10% to the capacity of a drive. And, as posted elsewhere, most OSes do 4K transfers most of the time.

Re:So only XP is out of luck?

[kill-1]

The new hard drives will have a compatibility mode. It will be slower though because it has to read-modify-write behind the scene.

Re:So only XP is out of luck?

[lorenlal]

Eventually, you have to put a line in the sand. If you push off the deadline, manufacturers will still take their time, and they'll be in the same place 9 years and 11 months from now.

Example: IPv6.

Re:So only XP is out of luck?

[alen]

MS has a clear support policy. Maybe you like Apple's 3 year support policy better than Microsoft's 10 year 7/3 policy?

Re:So only XP is out of luck?

[drinkypoo]

Except that pretty much every OS in use now has IPv6 support.

Except that name resolution is broken for IPv6 on Windows XP, which is the operating system not supporting 4k sectors that people are complaining about... so IPv6 was a super shitty example for you to try to defend.

Re:So only XP is out of luck?

[Sir_Lewk]

That's ok, the linux policy of free upgrades more than makes up for that for me.

But hey, you're a known troll, logic doesn't have much to do with this does it?

Re:So only XP is out of luck?

[AlecC]

The ECC (Error Check and Correct) is used for error correction. But generally speaking, the number of bits needed to check a block of data rises slower than the number of bits in the data - probably as the log of the number of bits, though I don't know. So grouping up sectors and providing a slightly longer ECC will save a significant number of the ECC bits. Of course a sector having eight times as many bits is eight times as likely to get corrupted, simply because of its size. But such faults are rare, though not rare enough to ignore. Of course, it will be a fraction less reliable. But the manufacturers do reliability/performance trade-offs all the time, and this is only one more of them. Presumably they reckon they have the reliability under control. If you want greater reliability, you need RAID anyway - to protect against drive failure as well as localized corruption. The probably reckon that anybody with really valuable data will be RAIDed anyway,

Re:So only XP is out of luck?

[moonbender]

ECC is more efficient for 4k blocks. Apparently, 100 bytes of ECC for a single 4k block are as reliable as 320 bytes of ECC for eight 512 byte blocks. See http://www.anandtech.com/storage/showdoc.aspx?i=3691

Re:So only XP is out of luck?

[kbielefe]

Sidestepping your ignorance or deliberate deception on periods of typical Linux support contracts, it still amazes me that comments touting Microsoft support periods continue to appear on articles like this. Who cares if support goes out 10 years if you can't buy a new hard drive that will work with the OS? It's articles and comments like this that give me difficulty discerning what exactly Microsoft "support" entails. A warm fuzzy number you can call where they say you have to upgrade to Windows 7 for that hardware to work?

Re:So only XP is out of luck?

[Leebert]

That's ok, the linux policy of free upgrades more than makes up for that for me.

You know, in a production computing environment, the cost of the software is pretty darn close to the least significant part of the costs of an upgrade, right?

Re:So only XP is out of luck?

[fprintf]

So some enterprising young person will be the first to invent IPv6 for Windows XP just like Trumpet Winsock was cobbled onto Windows 3.1 to provide Internet access way back before Win95. If there is some compelling reason to join in IPv6 network then such capability will be built.

Re:So only XP is out of luck?

[Antique Geekmeister]

Most used or not, it's 8 years old, and the update cost of a newly purchased machine with a plain OS installation disk includes roughly 2 Gig of downloaded data, and at least 5 reboots. (Measured last week on a clean installation of Windows XP Pro.) Even popular games that are shipping now do not run under it: that tells me it's obsolete.

Re:So only XP is out of luck?

[Idiot with a gun]

I've never understood this long living love for XP. The longer I work with it (I'm a support tech), the more I hate it. It genuinely has the feeling of an OS that was organically grown, without any fore planning. Wireless control often ends up in the hands of a user-space program instead of in the OS (wtf?), and updates are done through a god awful activex webpage. Blech. The long term (and even short term) stability of XP these days is poor at best, and I have no clue why everyone claims to love it.

On the other hand, most people I've met who make fun of Vista, never used it. My dad was slamming it earlier "Did you ever use it?" "... No". The vast majority of complaints about it stemmed from 2 problems:

• The so called "power users" always complain about any change, regardless of whether or not it's good.
• Underpowered machines were marked as "Vista Capable" when they were not.

And to honest, 7 is quite good. This is coming from a die hard Linux user (who actually liked Gentoo).

Re:So only XP is out of luck?

[pz]

The ECC (Error Check and Correct) is used for error correction.

ECC stands for Error Correcting Code, as per the original derivation from number theory. Only recently has the more breathy, marketing-friendly version come into use.

Re:So only XP is out of luck?

[lorenlal]

VESA as in the VESA Local Bus:
http://en.wikipedia.org/wiki/VESA_Local_Bus

This was a motherboard slot, it was basically an extended ISA slot.

Re:So only XP is out of luck?

[petermgreen]

Sidestepping your ignorance or deliberate deception on periods of typical Linux support contracts
He didn't say if he was stating lengths from release or length of overlap (to me the latter is the more important figure)

Who cares if support goes out 10 years
It's 10 years (5 mainstream, 5 extended) minimum from release, 7 years (2 mainstream, five extended) minimum overlap between releases and 2 years (all extended) minimum overlap if you skip a release. IIRC XP will have exceeded all of those.

if you can't buy a new hard drive that will work with the OS?
These "advanced format" drives will work fine with XP, they just require a little extra effort (either using a third party paritioning tool, fitting an extra jumper to change the sector mapping or using the WD tool to realign the partitions after setup) if you want maximum performance. Besides I can still by PATA drives so I doubt these drives will be the only ones on the market any time soon.

Similarly if I go to almost any major vendor I can still get computers and computer parts that are supported with XP, some of the consumer crap isn't but virtually every buisness machine and seperately sold peice of hardware i've seen lists XP as supported.

It's articles and comments like this that give me difficulty discerning what exactly Microsoft "support" entails.
For most of us the most important part of the support is continuation of security updates (though they have occasionally refused to release one that they really should have released by claiming that it's not nessacery in a default environment), I would be very uncomfortable running exposed systems (and I coun't any machine used to browse the web as exposed) on an OS that was no longer getting security updates.

There is also problem support and non-security hotfixes (free if created while in mainstream support, pay for if created during extended support) but for most of us these are fairly irrelevant.

As I alluded to above though what really matters is support from third party vendors, I can still buy the latest hardware and run XP on it with no problems, just try doing that with a comparable aged linux distro (e.g. debian woody).

Re:So only XP is out of luck?

[hkmwbz]

Who cares if support goes out 10 years if you can't buy a new hard drive that will work with the OS?

How is it Microsoft's fault if new hardware isn't working with XP?

WD is already shipping them

[daha]

There are certain models of the Western Digital Caviar Green drives that are already shipping with a 4K sector size, such as this one: http://www.newegg.com/Product/Product.aspx?Item=N82E16822136490

Re:Care to provide examples?

[DeHackEd]

I just checked my system. /dev/sda1 is /dev/sda + 32256 bytes, which is 63 512-byte sectors. /dev/sda2 is also on an odd-numbered sector alignment.

Fedora 11 fresh install, which is less than a year old.

Re:Care to provide examples?

[andrewd18]

I realize this is Slashdot, but both of the articles linked talk about the affected operating system. Hint: It shares an ending with a colloquial name for urine.

Isn't this just a firmware change?

[SharpFang]

It doesn't sound like the 512 bytes per sector is tightly bound to hardware. More like a low-level reformat plus change of some #defines in the firmware to transform from one to another type. Which would mean there could be i.e. a jumper setting for sector size, allowing for backward compatibility.

Also, the fact an OS doesn't enforce partition alignment doesn't mean it won't respect a disk formatted to aligned partitions. Just provide a 3rd party partitioning tool that aligns the partitions right, and install the OS on pre-made partitions. If your business depends on WinXP so much, your IT dept should be capable of doing it.

Re:Care to provide examples?

[tepples]

I realize this is Slashdot, but both of the articles linked talk about the affected operating system. Hint: It shares an ending with a colloquial name for urine.

Wii? PSP?

Re:intelligent interfaces

[tepples]

Why does the sector size presented by the interface have to reflect anything about the hardware?

If the OS clusters aren't aligned to physical sectors, the hard drive's controller has to read-modify-write all the time.

disable ECC?

[Anonymous Coward]

I heard some talks from the ZFS folks at Sun about how they were floating the idea to HD mfgr's of just disabling ECC on the drives. ZFS checksums every block, and in a RAID configuration, it would be able to transparently correct any checksum errors. I think this may have also been the motivation behind bringing triple-redundant RAID to ZFS.

The motivating idea was that this would reduce the overhead involved on ECC and gain extra space.

Thoughts?

Re:disable ECC?

[MobyDisk]

That wouldn't work with existing file systems that assume the drive does this. That's like deciding to remove the checksums from TCP and IP because a few protocols provide their own checksums. Might work in specialized cases. Probably just adds risk though for no benefit.

Re:disable ECC?

[Waffle Iron]

It doesn't seem like a great idea to me. There are a lot of different ECC algorithms and implementations. It seems to me that it would be better to let the hard drive manufacturer select one that closely matches the expected signal and noise characteristics of a particular disk drive rather than some generic algorithm in the filesystem.

Re:disable ECC?

[Jeff DeMaagd]

I can see this working for drives made specifically for RAIDs. Lose ECC on single drive configurations and you're asking for trouble. At least for RAIDS, a controller would need to be aware of this and do the remapping themselves, in the end, I don't know if it's worth doing this at all. If some enterprising RAID controller company could prove it works better to do it this way, then I can see it happening.

Re:disable ECC?

[Junta]

That's like deciding to remove the checksums from TCP and IP because a few protocols provide their own checksums.

Funny you should mention IP checksums, that's one feature removed from the IP layer in IPv6 precisely because the 'important' protocols do it themselves anyway (i.e. TCP).

Re:disable ECC?

[TheLink]

If they really did that, I'd say they were clueless. Such a feature would increase the odds of error.

ZFS might checksum every block. But what happens when ZFS is not everywhere? Does the BIOS or whatever equivalent support ZFS checksumming for reading the boot sectors? So those sectors better be 100% or you better be turning it off for boot drives. You have to use ZFS everywhere and for everything. For example, if you ever try to image a 1TB disk without ECC, the odds of bit errors will be high. Even if ZFS can repair it - you'd only find out much later (too late?) and likely after another error prone write.

Such a feature would just be creating more opportunities for people to get things wrong.

And for what benefit?

> The motivating idea was that this would reduce the overhead involved on ECC and gain extra space.

I think the people who'd want ZFS or RAID would rather have better reliability than the 10% or so extra space.

Even if they don't know it at first ;).

Re:disable ECC?

[butlerm]

That's insane. ECC at the hardware / firmware level corrects the vast majority of bit errors transparently in a manner that is invisible to the operating system. If you took out sector level ECC, the drives would be useless in anything other than a ZFS RAID configuration, and even then performance would drop in the presence of trivially ECC correctable errors, due to the re-reads and stripe reconstructions at the filesystem level.

Drive performance would probably drop because the heads would have to stay in closer alignment without the ability of ECC to correct data read errors caused by small vibrations and electrical noise. In addition, sector relocations would probably increase because tiny flaws that do not impair the ability of a drive to write an ECC correctable sector would force the drive to remap that sector to another part of the disk.

It is a similar issue with various wire level data transmission schemes. If DSL connections did not use error correcting codes, they would suffer much higher packet loss rates than they do now, especially at distance. Most those packets would generally get retransmitted due to transport level checksum errors, but why resort to performance impairing fall back measures when the problem can be largely eliminated at a lower level?

Re:disable ECC?

[Izmunuti]

Ugh. Sounds like a bad idea. Hard drive channels are noisy. How will ZFS fare if lots and lots of sectors read from every drive have at least a couple of bits in error? With no ECC in the drive, errors would be common.

Re:disable ECC?

[Anonymous Coward]

One of the reasons there is so much BS and hype surrounding ZFS...

Drives already do and have for years done error correction and most revector badblocks dynamically and the OS never even knows. It's part of how drives are so reliable as it is. Pushing that logic up in to the filesystem just introduces more complexity to the filesystem and reduces overall reliability.

Talk to any drive engineer, what they want the most is for filesystem engineers to stop trying to outsmart the drive guys. THere is not a guaranteed relationship between a sector and it's location on the disk, the drive and the firmware it has will try to figure that out the best way it can.

What they really should spend their time on is filesystems and their relationship with cache will have to change in the next decade, solid state medias don't need caching the same way disks do, I fully expect disks to start coming as hybrid devices with solid state storage and disk based storage as a singular device. There are some relatively complex problems to solve to provide media awareness to all the storage algorithms.

Re:disable ECC?

[drinkypoo]

If you were going to eliminate ECC in one place or another, it wouldn't be on the drive. The drives have to operate in the real world of analog states, while the filesystem works in the virtual world of "whatever the disk actually feeds me". Disks have to have correctable ECC just to reliably give you accurate data from magnetic media at these densities. It would make more sense to upgrade the on-disk ECC and give the filesystem better access to the disk's ECC.

Why are there sectors?

[AP31R0N]

i'm asking because i don't know, not to troll.

What is their purpose? Does the purpose still matter?

Re:Why are there sectors?

[JordanL]

A sector on a HDD is the minimum writeable space. Think of it as a lot in a subdevelopment. If each lot is 50,000 sq. ft. on a 20 acre plot, and you move to 60,000 sq. ft. lots instead, the plot is still 20 acres, but the development now has less lots on it.

In computers, larger sectors are often better for large files, while smaller sectors are better for smaller partitions and smaller files. If a sector is 4096 bytes, and you create a 1024 byte file, it still occupies 4096 bytes on the disk, as the HDD won't write anything else but that file to the sector. If you have files that are hundreds of megabytes though, you can access the file, with minimum wastage, by using fewer sectors, which reduces thrashing and similar issues.

The discrepancy between file sizes and sector sizes is what the difference is in Windows when you view a hard drive and it displays "size" and "size on disk". "Size" is the actual file size, while "size on disk" is the amount of space the file occupies on the hard drive.

Re:Why are there sectors?

[JordanL]

It is indeed. Unless HDD makers were going to create firmware, and programmers made partition formats, which address each bit individually (which itself would require an enormous amount of space... much larger than the HDD in fact), you will always be unable to live without sectors. The subdivision idea is again relevant. Imagine if every part of the 20 acre plot had to be "addressable" down to the square inch.

Re:Why are there sectors?

[DarkOx]

You are confusing physical sector size with cluster size. May file systems are already addressing data in larger blocks. 4096 is very commonly used. They are generally multiples of 512 which is the physical sector size; so that its is easy to calculate the physical sector that needs to be changed when you know the logical.

Its quite possible to have a cluster size smaller than the sector size; the file system would need to be smart enough to determine what other clusters fall on that sector and write them all though.

Re:Why are there sectors?

[Thanshin]

So why have the sectors at all? [...]
The 1024 byte file could then take 1024 bytes.

That's not "not having sectors", that's having sectors 1 byte long.

Thus, apply the reasoning of "bigger sectors, faster treatment of bigger files, and vice-versa".

Re:Why are there sectors?

[AP31R0N]

Ah, so it's saying, "Turn left on Evergreen... it's on that block". And the monstrous estate is from Elm to Fern at State. As opposed to GEOCOORD 32'57"(bunchOfDigits) by 32'57"(more digits).

Got it.

With the 1024 byte example, could the address just be "from bit X to bit X+1023"? i guess that too would be too much. All those tiny .dlls and .inis would take more space to define than they actually take.

Thanks!

Re:Why are there sectors?

[TheRaven64]

Yes, it's an addressing thing. The grandparent is confusing sectors with allocation units. A filesystem is perfectly at liberty to allocate sub-sectors to different files (some do). A 32-bit disk interface can address 2^32 sectors. If you have one-byte sectors then that means you're limited to 4GB disks. If you have 512 bytes sectors then you're limited to 2TB. If you want a disk bigger than 2TB then you can either make the interface wider or can make the sector size bigger. Making the address wider requires defining a new interface[1], although ATA currently supports 48-bit addresses, so this isn't really a problem for a while. It is convenient for filesystems, because they can continue to use 32-bit sector indexes for partitions larger than 2TB.

The real advantage of bigger sectors is that they reduce the command overhead. To write 4KB to the disk you just need to send one write command and the data, rather than eight. All modern operating systems cache data from disk in RAM and so will write it out or read it in as a group of pages. The smallest page size of any modern architecture is 4KB, so having 4KB sectors is a lot more convenient.

use of current cultural context....

[Himring]

This may not be a smooth transition, because some OSes do not align partitions on 4K boundaries.

"One life ends; another begins"

Re:Looks like 512

[butlerm]

Those are "logical" sectors, which can be different from the physical sector size. According to the Anandtech article the Western Digital hard drive model numbers that end with "EARS" use the larger, 4KB physical sector size, while presenting a 512 byte logical sector size to the operating system for compatibility reasons.

Please note, of course, that the logical sector size is a drive interface level concept distinct from the filesystem cluster or block size. Filesystem block sizes have generally been larger than the logical or physical sector size for quite some time.

Re:intelligent interfaces

[Thanshin]

Do you really believe your hard drive has 256 heads?

It had only six, at first, but we didn't know the thing about burning the stumps.

Re:Care to provide examples?

[Gulthek]

It took me longer than it should've to answer this riddle. Shortcut for the similarly caffeine deprived: andrewd18 means "P" as in Windows XP.

Seriously, I was like "Win...dows?" "U...nix?" "Micro...soft?" "OS...X"? "BS...D"?

Tail packing

[tepples]

Unless HDD makers were going to create firmware, and programmers made partition formats, which address each bit individually (which itself would require an enormous amount of space... much larger than the HDD in fact), you will always be unable to live without sectors. The subdivision idea is again relevant. Imagine if every part of the 20 acre plot had to be "addressable" down to the square inch.

It's called block suballocation: store a small file in its entirety in another file's slack space. And yes, it's a "killer" feature.

Re:Tail packing

[Hatta]

So, I guess Hans Reiser has a lot of experience with tail packing then.

Re:Care to provide examples?

[Anonymous Coward]

Solar... isssss

D:

Re:Paying for More Slack Space.

[butlerm]

Any change in sector size that doesn't affect the filesystem block size will not affect the number of KB required to store a file at all. Since virtually every filesystem already uses 4 KB block sizes by default a change to 4KB logical or physical sector sizes will not have an effect on storage requirements.

Actually no.

[Mashiki]

Most of the drive manufactures are releasing tools to align the drives to 4k clusters so they can be used under XP. WDC already has theirs out here: WDC Adv Format Plus instructions on all of their new 1TB and higher drives on how to set them up properly. You do have to jumper them, then format them specially but the drives work fine with 4k clusters. I put one in my work machine on Saturday, works flawlessly.

*I only used WDC because that's the brand I picked up recently. I do know other companies have similar tools and jumper settings on their newer drives as well.

Re-Format old drives?

[Mojo66]

Are there tools to low-level format 512-byte drives into 4096-byte ones? I gather this would increse capacity by 13%.

Re:Re-Format old drives?

[butlerm]

This would require a firmware change, and for SATA drives, it is just not going to happen. High end SCSI drives maybe.

Re:Isn't this just a firmware change?

[butlerm]

NTFS has been 4K aligned for a long time now.

That doesn't do any good if the partition it is on starts with an LBA that is not a multiple of 8. Windows versions prior to Vista create the first partition starting at LBA 63, which is not 4KB aligned.

The people who will have performance problems will primarily be Windows XP users who purchase the newer style drives and do not realign the first partition accordingly. Some versions of "fdisk" on Linux have a similar deficiency, with an "cylinder" based user interface and odd size cylinders in the name of MSDOS compatibility. Not sure if that has been fixed yet.

Re:Moot Point

[Archangel Michael]

I do believe those are carry overs from Magnetic Media. There is no need for it to be that way (I think).

My point, was more or less, that we'll need to RETHINK how we define things. SSD will become more of an extension of the Operating Space we call "RAM". Much like we now have RAM, L2, L3, and L4 cache (and even maybe RAID Cache) are now.

I think, and this is just my opinion at this point, that we'll start to name memory by nearness to the Core(s), and SSD will join that space.

I'm not sure we need block level devices any longer. It will require re-thinking much of how we view things no doubt, but I think it is inevitable at this point.

Re:Windows XP end-of-life?

[Jim Efaw]

Well, it's in Extended Support which for one thing means MS doesn't give a rats ass whether or not XP works with the more efficient AF HDDs, since that's not a security related patch.

Well, that's a fair assessment. Of course, that's a monopoly tactic — any business that dropped support for that widespread of a product in a legitimate competitive environment would find themselves with no customers for the newer product because customers would be trying to migrate out from under that vendor at all costs.

ECC is NOT linearly proportional

[A nonymous Coward]

See the comment below. It takes 320 bytes for 8 512-byte ECCs, only 100 bytes for a single 4096-byte ECC.

Characters were not always 8-bit

[klubar]

I believe that some of the early CDC machines (a company that is no longer around) had a 6-bit character. The Digital Equipment Company (DEC, alos a company that is no longer around) PDP-1, maybe the PDP-20, and some others also had a 6-bit character. The PDP's had 36-bit words, packing 6 characters into a word. And of course, the IBM machines (a company that is still around) used EBCDIC rather than ASCII (but did use an 8-bits per character). Some of the earlier (and even the 370's) IBM machines used BCD (binary coded decimal) for arithmetic (packing a number from 0 to 9 in 4 bits, with some sign and unassigned bits left over).

Also, back in the IBM JCL days, when allocating disk space for a file you could specify the number of cylinders (or tracks) that you wanted, the block size and the packing factor.

Re:Characters were not always 8-bit

[VGPowerlord]

As strange as it may seem, there actually is precedence for 8-bit bytes... in Currency of all places.

The Spanish Milled Dollar was often split into eight pieces to make change. Hence the term "Pieces of Eight."

However, for whatever reason, those were often termed bits in the US. So, there were 8 bits to the Spanish Milled Dollar.

And two bits made up a quarter-dollar, hence the "Shave and a hair cut... two bits!" routine.

Re:Characters were not always 8-bit

[Babylon Rocker]

It was even worse than that on the PDP-10s.... The operating system used both SIXBIT characters and 7-bit ASCII characters using variable-length bit-field instructions (36 bit words => 5 chars and 1 bit left over).

please stop spreading FUD

[Anonymous Coward]

What a bunch of misinformed drivel. That article is missing a couple of things:

firstly) The issue affects all Windows versions based on a 5.x kernel. That means Windows 2000, XP, 2003 server and Windows Home Server.

1) These drives are NOT strictly-4k-sector. The platters may be organized in 4k sectors, but the drive only talks to the OS in terms of 512 byte-sectors. And since we're discussing old Windows versions: NTFS has defaulted to using 4k (logical) sectors since its introduction, so there is NO performance penalty when using NTFS on these drives. You shouldn't be using FAT32 anyway.

2) The issue can be worked around by creating partitions with a tool that understands 4k sectors, or by re-aligning the partitions after creation/installation. If you only use a drive in those systems (i.e. no repartitioning), the drive will work as it should. Even if you create partitions that are unaligned, the drive will still work - you will only lose some performance.

3) The one genuine problem raised in the linked article comes when you want to use these drives in closed-firmware devices. In this case you still have two options: either you use the WD-provided jumper setting, or you pre-create the partitions before you insert the drive.

I fail to see what the fuss is all about.

Re:Time to Eliminate this problem

[butlerm]

Making the drive handle things at the file level is the equivalent of turning it into a NAS device where the system software would generally be inaccessible, unmodifiable, and un-upgradeable, unfortunately. It would still be an interesting engineering challenge, of course.