From: Jeff Garzik <jgarzik@pobox.com>
To: Valdis.Kletnieks@vt.edu
Cc: Chip Salzenberg <chip@pobox.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.3-rc3 - IDE DMA errors on Thinkpad A30
Date: Sun, 15 Feb 2004 23:09:52 -0500 [thread overview]
Message-ID: <40304290.7090207@pobox.com> (raw)
In-Reply-To: <200402160358.i1G3wC6W013389@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Sun, 15 Feb 2004 22:47:37 EST, Jeff Garzik said:
>
>>One for the todo list, I suppose... a useable workaround for this is
>>probably good ole 'e2fsck -c', i.e. badblocks... That says "check again
>>to see if this sector is bad", and -hopefully- will unmark bad blocks
>>that were incorrectly marked bad.
>
>
> Does e2fsck/badblocks issue the right ioctls/etc to make the disk read the
> *original* block, or will the disk simply check the *redirected* block?
I'm not sure your question has meaning.
Consider: ext2 reads sector 1234. drive returns "media error", and
then swaps the bad sector for a good one. Reboot and run badblocks.
badblocks reads sector 1234, in whatever manner the drive chooses to
present sector 1234 to the OS.
"original" versus "redirected" block is invisible to the OS. The OS
only knows that an event occured at a single point in time -- the media
error.
Jeff
next prev parent reply other threads:[~2004-02-16 4:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1pliv-6ya-5@gated-at.bofh.it>
2004-02-15 15:22 ` Linux 2.6.3-rc3 - missing IDE hunk from bk4; good or bad? Chip Salzenberg
2004-02-15 15:58 ` Bartlomiej Zolnierkiewicz
2004-02-15 16:34 ` Linux 2.6.3-rc3 - IDE DMA errors on Thinkpad A30 Chip Salzenberg
2004-02-15 17:08 ` Bartlomiej Zolnierkiewicz
2004-02-16 0:55 ` Chip Salzenberg
2004-02-16 2:14 ` Jeff Garzik
2004-02-16 3:37 ` Chip Salzenberg
2004-02-16 3:47 ` Jeff Garzik
2004-02-16 3:58 ` Valdis.Kletnieks
2004-02-16 4:09 ` Jeff Garzik [this message]
2004-02-16 4:29 ` Valdis.Kletnieks
2004-02-16 12:06 ` Bill Davidsen
2004-02-16 4:08 ` Chip Salzenberg
2004-02-16 4:24 ` Bartlomiej Zolnierkiewicz
2004-02-16 19:27 ` Eric D. Mudama
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=40304290.7090207@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=chip@pobox.com \
--cc=linux-kernel@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