You are not logged in.

#1 2010-07-02 06:27:31

RedShift
Member
From: Belgium
Registered: 2004-07-16
Posts: 230

ATA command timeouts after disk has gone sleeping

Hi all


I've configured myself a NAS, which is infrequently accessed, so I set the standby timer of the disks to 241 (30 minutes) using hdparm.

for i in /dev/sd?; do
    hdparm -S 241 $i > /dev/null
done

After 30 minutes the disks go to sleep, no problem there, but once they are accessed again, the first command sent to the disk time out:

ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata7.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
         res 40/00:00:00:f1:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata7.00: status: { DRDY }
ata7: hard resetting link
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata7.00: max_sectors limited to 256 for NCQ
ata7.00: max_sectors limited to 256 for NCQ
ata7.00: configured for UDMA/133
sd 6:0:0:0: timing out command, waited 7s
ata7: EH complete
SCSI device sdg: 1953525168 512-byte hdwr sectors (1000205 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: drive cache: write through

After that the drives work fine again. The command timeout is 7 seconds, which seems too low because the disks need some time to spin up.

Two questions:

Can the ATA command timeout be increased?

If the command fails, is it retried?


Thanks,

Glenn


:?

Offline

Board footer

Powered by FluxBB