Hello, On 12/21/2009 01:34 PM, Tejun Heo wrote: > (cc'ing Kay and Lennart. Hello.) > > A proper solution would be.... > > * Build database of load cycle limits and useable APM values on drive > models. The former shouldn't be difficult. Each vendor carries > only a few product lines at any given time and publish datasheets on > the webpage. Plus, all the mobile drives I've seen are rated for > 600,000 cycles. The latter may be a bit more tricky. Depending on > drive model, certain APM values simply don't work (e.g. 255 means > max power by spec but some firmwares wrap the value and recognize it > as min power), some values overheats the device and so on. In most > cases the value 254 seems safe tho. storage-fixup.conf should be > useable as the source for useable values, I think. > > * Monitor load cycle count by smart commands and if it continues to > increase at an excessive rate (e.g. such that it reduces uptime to > under a year), warn the user and configure higher APM value. > > As this problem mostly happens on laptops, I think it's probably best > to handle this from the new desktop disk management thing so that the > user can be warned. Do you think it's feasible to handle this from > devkit? Lennart, any thought on this? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
