>
>
> Seems pretty much a non-issue. It's not because of Linux (you're
>
> just reading about it on a kernel forum :-), but because of a buggy interaction
>
> between certain laptop IDE drives and power management. It seems to depend
>
> on the installation platform as well as the particular drive since manifestation
>
> is dependent on IO patterns.
>
Uhm I agree, it isn't a kernel's bug, or a linux issue, but for what I've understood seems a non-standard use of ata commands (probably specific vendor extensions).
In particular with newer hdds, to obtain best performance in power saving and to make them more shock resistent head's device should be parked when disk is unused for a time.
In practice, the result is that if s.o. is booted by the hdd it (in transparent manner , to user) continuosly accesses to hdd.
The Device doesn't understand correctly commands relatively poer save management, has false beliefs on the world, and it cycles to parks unparks the heads (with deleterious effects on hdd's life).
>
>
> The issue here with WD is that WD chooses to require their own
>
> special program to reset APM parameters on a few models (I'm not sure you can
>
> use hdparm on their "Green" drives). That could be seen as "incompatibility"
>
> but it's really WD's choice to support only Windows. That's a good reason
>
> to avoid WD.
of course, after this experience, I will avoid them.
The Support center has told me simply:" here there are utilities for your model, with which you can diagnose the hdd health (note: I've just told them smart count load/unload, make diagnose wasn't my problem), there aren't fix for firmware, for your model there aren't software to tune this problem, but there is for others models, and has gave me the link, but also told me that this was not supported by WD ( looking on web, other users have reported that seems don't work)
> If you end up with a set of hardware that manifests this bug
>
> it's not really a big deal, and can be worked around easily with hdparm.
ok, is correct , in my experience I've used this utility and its .conf file, stopping the autopark function.
But honestly, I'm not sure of the consequence on policy's device power save managing (certainly, when the machine goes in stand-by, also hdd goes, but I seems that hdd can make a smart use of power, for example when it's not fully used)
>
> Frankly, you can avoid all these kinds of things by using last
>
> generation hardware for Linux. Older stuff is well supported and Linux
>
> doesn't need the latest hardware to run rings around Windows systems.
I'm not sure to understand your suggest (this only because English isn't my language, excuse me): Yuo suggest me, to avoid these problems, to prefer old hardware (probably without the cited smart parking feature )