From: Mike Accetta <maccetta@laurelnetworks.com>
To: linux-ide@vger.kernel.org
Subject: Re: ICH6-M libata disk timeouts 2.6.18 -> 2.6.19
Date: Fri, 12 Jan 2007 22:09:47 -0500 [thread overview]
Message-ID: <27103.1168657787@mdt.dhcp.pit.laurelnetworks.com> (raw)
In-Reply-To: Your message of "Sat, 13 Jan 2007 11:23:19 +0900." <45A84297.3020408@gmail.com>
Tejun Heo wrote:
> 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 /sys/block/sdb/device/queue_depth to 4 the raid1
> > re-sync completes without incident. When set to 5 it eventually gives
> > the timeout error message (although at well past 50% of the re-sync).
> > The problem was originally observed with the default setting (31).
>
> Please post the result of 'hdparm -I /dev/sdb'. Thanks.
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
Model Number: FUJITSU MHT2060BH
Serial Number: NR0YT53258G8
Firmware Revision: 0000104A
Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 117210240
LBA48 user addressable sectors: 117210240
device size with M = 1024*1024: 57231 MBytes
device size with M = 1000*1000: 60011 MBytes (60 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 254, current value: 254
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
* Automatic Acoustic Management feature set
SET MAX security extension
* Advanced Power Management feature set
* DOWNLOAD MICROCODE cmd
* General Purpose Logging feature set
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
60min for SECURITY ERASE UNIT.
Checksum: correct
--
Mike Accetta
ECI Telecom Ltd.
Data Networking Division (previously Laurel Networks)
next prev parent reply other threads:[~2007-01-13 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 23:16 ICH6-M libata disk timeouts 2.6.18 -> 2.6.19 Mike Accetta
2007-01-10 4:56 ` Mike Accetta
2007-01-13 2:23 ` Tejun Heo
2007-01-13 3:09 ` Mike Accetta [this message]
2007-01-19 2:49 ` ICH6-M libata disk timeouts in 2.6.19 (except with small queue depth) Mike Accetta
2007-01-20 18:21 ` Tejun Heo
2007-01-22 16:04 ` Mike Accetta
2007-01-23 3:11 ` Mark Lord
2007-02-27 14:54 ` ICH6-M libata disk timeouts 2.6.18 -> 2.6.19 Tejun Heo
2007-02-27 19:37 ` Mike Accetta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27103.1168657787@mdt.dhcp.pit.laurelnetworks.com \
--to=maccetta@laurelnetworks.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).