Re: ICH6-M libata disk timeouts 2.6.18 - 2.6.19

2007-02-27 Thread Tejun Heo
Mike Accetta wrote: The version of hdparm on this box gives dev/sdb: operation not supported on SCSI disks against the SCSI disk name. With the controller in compatible mode, here is the 'hdparm -I /dev/hdb' output on the same disk: ATA device, with non-removable media

Re: ICH6-M libata disk timeouts 2.6.18 - 2.6.19

2007-02-27 Thread Mike Accetta
Tejun Heo writes: Mike Accetta wrote: The version of hdparm on this box gives dev/sdb: operation not supported on SCSI disks against the SCSI disk name. With the controller in compatible mode, here is the 'hdparm -I /dev/hdb' output on the same disk: ATA device, with

Re: ICH6-M libata disk timeouts 2.6.18 - 2.6.19

2007-01-12 Thread Tejun Heo
Mike Accetta wrote: Here's a bit more information on these timeouts. I noticed a mention of changing the command queue depth in a recent lkml post and decided to give that a whirl. This problem seems to be related to the depth of the queue. When I set the value for

ICH6-M libata disk timeouts 2.6.18 - 2.6.19

2007-01-09 Thread Mike Accetta
We have a system with an ICH6-M controller and two SATA drives configured for software RAID1. Under 2.6.18, adding the second drive to the array and starting a re-sync would go to completion without incident. Under 2.6.19, adding the second drive will always eventually generate what appear to be

Re: ICH6-M libata disk timeouts 2.6.18 - 2.6.19

2007-01-09 Thread Mike Accetta
Here's a bit more information on these timeouts. I noticed a mention of changing the command queue depth in a recent lkml post and decided to give that a whirl. This problem seems to be related to the depth of the queue. When I set the value for /sys/block/sdb/device/queue_depth to 4 the raid1