From: Daniel Drake <dsd@gentoo.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-scsi@vger.kernel.org
Subject: 2.6.27 looping on SCSI errors for bad sectors
Date: Thu, 11 Dec 2008 20:36:51 +0000 [thread overview]
Message-ID: <494179E3.30802@gentoo.org> (raw)
Hi Alan,
I'm aware of your work at http://bugzilla.kernel.org/show_bug.cgi?id=11843
I agree with fixing the unusual_devs file for USB devices that report
the wrong capacity, but this SCSI "looping on error" problem reaches
further than that. Gentoo has a bug report at
https://bugs.gentoo.org/show_bug.cgi?id=248698 where there is a "real"
bad sector in the middle of a disk, and this bug is affecting recovery
of said disk.
On the kernel bugzilla you posted some patches that would improve the
behaviour of 2.6.27 here. Are those patches candidates for 2.6.27.x, or
do you know if it's being fixed another way, or is it a lost cause?
I understand that 2.6.28 has been fixed through a major rework in that area.
Thanks,
Daniel
next reply other threads:[~2008-12-11 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 20:36 Daniel Drake [this message]
2008-12-11 22:02 ` 2.6.27 looping on SCSI errors for bad sectors Alan Stern
2008-12-11 23:05 ` Oliver Neukum
2008-12-12 14:46 ` Alan Stern
2008-12-12 12:12 ` Daniel Drake
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=494179E3.30802@gentoo.org \
--to=dsd@gentoo.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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