Custom Query (1386 matches)
Results (181 - 183 of 1386)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #306 | fixed | Please add Crucial M4 *SSD1 drives | ||
| Description |
Crucial has M4 *SSD1 drives models in addition to *SSD[23], existing in database. Please add this modification. Patch is attached. |
|||
| #308 | fixed | intel 530 ssd db entry | ||
| Description |
Intel 530 series are not in DB. Here I'm attaching diff, with updated attributes from Intel documentation about the drive |
|||
| #310 | fixed | Support staggering of drive tests | ||
| Description |
On the mailing list a best practise thread popped up asking about test cycles which brought us to DEVICESCAN and the staggering of these tests when you have many (4+) drives in a box. A: If a user feeds something like "(O/../../(7|3)/00|S/../.././12|L/../../6/03|C/../../7/03)" to DEVICESCAN it should use best effort to not send that command to every drive at once. It should probably assume something like +30% of a drives reported test runtime before triggering another drive. OR maybe the schedule is in "every X days" and not "sun-sat" calendar weeks per say. B: A sane default (one short test per day, one/two long test per week, one offline per week/month?) to be added commented of course to the default config file. |
|||
