Posted 10 January 2011
Original url:
http://forums.storagereview.com/ind...t-tlererccctl/page__view__findpost__p__266337
Both Linux and FreeBSD can use normal desktop drives without TLER, and in fact you would not even want TLER in such a case, since TLER can be dangerous in some circumstances. Read on.
What is TLER/CCTL/ERC?
TLER (Time-Limited Error Recovery
CCTL (Command Completion Time Limit)
ERC (Error Recovery Control)
These basically mean the same thing: limit the number of seconds the harddrive spends on trying to recover a weak or bad sector. TLER and the other variants are typically configured to 7 seconds, meaning that if the drive has not managed to recover that sector within 7 seconds, it will give up and forfeit recovery, and return an I/O error to the host instead.
The behavior without TLER is that up to 120 seconds (20-60 is more frequent) may pass before a disk gives up recovery. This behavior causes haywire on all Hardware RAID and Windows-based software/onboard/driver RAIDs. The RAID consider typically is configured to consider disks that don't respond in 10 seconds as completely failed; which is bizarre to say the least! This smells like the vendors have some sort of deal causing you to buy HDDs at twice the price just for a simple firmware fix. LOL!! Don't get yourself buttraped; read on!
When do i need TLER?
You need TLER-capable disks when using any Hardware RAID or any Windows-based software RAID; bummer if you're on Windows platform! But this also means Hardware RAID on any OS (FreeBSD/Linux) would also need TLER disks; even when configured to run as 'JBOD' array. There may be controllers with different firmware that allow you to set the timeout limit for I/O; but i've not yet heard about specific products, except some LSI 1068E in IR mode; but reputable vendors like Areca (FW1.43) certainly require TLER-enabled disks or they will drop-out like candy whenever you encounter a bad/weak sector that needs longer recovery than 10 seconds.
Basically, if you use a RAID platform that DEMANDS the disks to respond within 10 seconds, and will KICK OUT disks that do not respond in time, then you need TLER.
When don't i need TLER?
When using FreeBSD/Linux software RAID on a HBA controller; which is a RAID-less controller. Areca HW RAID running in JBOD mode is still a RAID controller; it controls whether the disks are detached, not the OS. With a true HBA like LSI 1068E (Intel SASUC8i) your OS would have control about whether to detach the disk or not; and Linux/BSD won't, at least not for a simple bad sector. Not sure about Apple OSX actually, but since it's based on FreeBSD i could speculate that it would have the same behavior as FreeBSD; perhaps tuned differently.
Why don't you want TLER even if your disks are capable?
If you don't need TLER, then you don't want TLER! Why? Well because TLER is dangerous! Nonesense? Consider this:
1. You have a nice RAID5 array on Hardware RAID, being a valuable customer you spent the premium price on TLER capable disks.
2. Now one of your disk dies; oh bummer! But hey i have RAID5; i' protected, RIGHT?
3. So i buy a new disk, and replace the failed one! So easy, ha ha!
4. Oh noooes! A bad sector on of the remaining member disks, and it caused TLER to forfeit; now i got an I/O error during rebuilding my degraded array and the rebuild stopped and i lost access to my data! Arrrrgh!!
The danger in TLER lies that if you lost your redundancy, then if a weak sector occurs that COULD be recovered, TLER will force the drive to STOP TRYING after 7 seconds. If it didn't fix it by then, and you lost your redundancy, then TLER is a harmful property instead of a useful one.
TLER works best when you got alot of redundancy and can swap disks easily, and want disks that show any sign of weakness - if even just a fart - to be kicked out and replaced ASAP, without causing hickups which are unacceptable to a heavy-duty online money transaction server, for example. So TLER can be useful, but for consumers this is more like an interesting way for vendors to make some more money from you poor souls!
What is Bit-Error Rate and how does it relate to TLER?
uBER or Uncorrectable Bit-Error Rate, has been steady at 10^-14, but capacities are growing and the BER rate stays the same. That means that modern high-capacity harddrives now are more likely to be affected by amnesia; they sometimes really cannot read a sector. This could be physical damage to the sector itself, or just a weak charge meaning no physical damage to that sector but just unreadable.
So 2TB 512-byte sector disks have a relative high BER rate. This makes them even more susceptible to dropping out of conventional Windows/Hardware RAIDs, and is why the TLER feature has become more important. But i consider it to be rather a curse than a blessing.
So.. explain again please; Why don't i need TLER on Linux/BSD?
Simple: the OS does not detach a disk that times out, but resets the interface and re-tries the I/O. Also when using ZFS, it will write to a bad sector, causing that bad sector to be instantly fixed/healed/corrected since writing to a bad sector makes the disk perform a sector swap right away. In the SMART data, the "Current Pending Sector" (active bad sector) would then become "Reallocated Sector Count" (passive bad sector which no longer causes harm and cannot be seen or used by the host Operating System anymore).
That includes ZFS?
Yes. ZFS is, of course, the most reliable and advanced filesystem you can use to store your files, right now. It's free, it's available, it's hot. So use it whenever you can.