From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <tj@kernel.org>, Andi Kleen <andi@firstfloor.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.6.34 PDC20268 PATA IO error loop makes system unusable
Date: Mon, 14 Jun 2010 13:29:52 +0200 [thread overview]
Message-ID: <20100614112952.GF17092@basil.fritz.box> (raw)
In-Reply-To: <20100614121753.5723eaa2@lxorguk.ukuu.org.uk>
On Mon, Jun 14, 2010 at 12:17:53PM +0100, Alan Cox wrote:
> > > sd 11:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > sd 11:0:0:0: [sdd] Sense Key : Medium Error [current] [descriptor]
>
> That is the drive complaining about a bad block.
>
> > > Descriptor sense data with sense descriptors (in hex):
> > > 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00
> > > 00 5b 23 bb
> > > sd 11:0:0:0: [sdd] Add. Sense: Address mark not found for data field
> > > sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 5b 23 4f 00 00 80 00
>
> Which in my experience usually comes from
>
> - The disc being unable to find the data block
>
> - A corrupt indirect block in the file system leading to a requst for an
> out of range data block
>
> In theory it could be an on the wire bitflip but thats a bit too
> consistent to believe.
Thank, Alan. I really don't care about the drive (nothing valuable on it).
It was an old IDE disk and I am not surprised it has some bad sectors.
In fact I was clearing it for junking it (although I may keep it now
just in case I need to test IDE error handling again :)
But I cared about the system becoming unusable due to error handling running
amok.
That was the point of this bug report.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-06-14 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 15:48 2.6.34 PDC20268 PATA IO error loop makes system unusable Andi Kleen
2010-06-14 7:43 ` Tejun Heo
2010-06-14 7:53 ` Andi Kleen
2010-06-14 7:59 ` Tejun Heo
2010-06-14 9:22 ` Andi Kleen
2010-06-14 16:20 ` James Bottomley
2010-06-14 11:17 ` Alan Cox
2010-06-14 11:29 ` Andi Kleen [this message]
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=20100614112952.GF17092@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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).