Oh.. The famous EARS drives. I missed this info in the
start of the thread.
Now, after this info, the whole thread is quite moot.
The thing is, for these WD*EARS drivers, it is _vital_ to get
proper alignment of all partitions and operations. They've
4Kb sectors physically but report 512bytes sectors to the OS.
It is _essential_ to ensure all partitions are aligned to the
4Kb sectors. Be it LVM, raid-something, etc - each filesystem
must start at a 4kb boundary at least, or else you'll see
_dramatic_ write speed problems.
So.. check the whole storage stack and ensure proper alignment
everywhere. In particular, check that your partitions are not
aligned to 63 sectors (512b), or starts at N+1 sector - the
most problematic mode for these drives.
And before anyone asks, no, these drives are actually very
good. With proper alignment it works very fast for both
reads and writes, despite it being 5400RPM. I have a 2Tb
drive from these series (WD20EARS) - despite numerous claims
that it does not work or works very slow with small files,
it's quite fast, faster than many prev-gen 7200 drives.
Yes, Sil 3114 does not support NCQ. But these drives does not
have good NCQ implementation either - apparently the Read-Modify-Write
logic has eaten NCQ which were traditionally good in recent WD
drives.
There's a utility (ms-dos based) to disable this feature for wd
ears drives, on their website.
No, this is about TLER. The "desktop" drives like this will try
re-read data in case of error, and if that does not work the
raid code will most likely declare the drive's dead and kick
it off the array. Drives which are supposed to work in RAID
config has configurable timeouts/retries, so that the RAID
code will be able to take care of read errors.
/mjt
--
