Custom Query (1359 matches)
Results (142 - 144 of 1359)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #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. |
|||
| #311 | fixed | Wiki FAQ page still points to old repository browser for drive.h | ||
| Description |
I noticed that the "drivedb.h" link found in the FAQ Wiki page,
, still points to the old repository browser rather than the new one (so when one follows the link one is taken an 8-month-old version of the file). Similarly, in the "Contribute to Smartmontools: Device Information" section of the Wiki homepage, , the "current version of smarmtontools drive database" link points to another (apparently obsolete) URL:
(though in this case it does automatically redirect to the "/p/smartmontools/code..." URL). It appears both these Wiki pages can only be edited by Admins, so I'm opening this ticket to request that. Thanks. Nathan |
|||
