Bruce/Tejun, Just so you both know, even when specifying '-n standby,q' in smartd, it still triggers timeouts on my system. The timeouts are no longer coming from the default half-hour checks, but from my configured self-test times with the '-s' option. It appears smartd overrides the '-n' parameter in this case, triggering the libata soft reset. This is another case that would be fixed if libata does the SRST automatically. Thanks, -Andrew Oct 11 02:16:52 (none) daemon.info smartd[23848]: Device: /dev/sdb, STANDBY mode ignored due to scheduled self test (47 checks skipped) Oct 11 02:17:03 (none) user.err kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Oct 11 02:17:03 (none) user.err kernel: ata2.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 Oct 11 02:17:03 (none) user.warn kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 11 02:17:08 (none) user.warn kernel: ata2: port is slow to respond, please be patient (Status 0xd0) Oct 11 02:17:10 (none) user.info kernel: ata2: soft resetting port Oct 11 02:17:10 (none) user.info kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 11 02:17:10 (none) user.info kernel: ata2.00: configured for UDMA/100 Oct 11 02:17:10 (none) user.info kernel: ata2: EH complete On 10/10/07, Tejun Heo <htejun@xxxxxxxxx> wrote: > Maybe what should be done is to track sleep mode in libata and issue > SRST automatically if a command is issued to a sleeping drive. I'll > work on it. - 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
