From: Chip Salzenberg <chip@pobox.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc3 - IDE DMA errors on Thinkpad A30
Date: Sun, 15 Feb 2004 22:37:40 -0500 [thread overview]
Message-ID: <20040216033740.GE3789@perlsupport.com> (raw)
In-Reply-To: <40302783.6020505@pobox.com>
According to Jeff Garzik:
> Really the best policy IMO is just to run 'e2fsck -c' every so often
> until you can get your data off this disk, and throw it in the garbage.
> That does the "remapping" at the filesystem level, which is IMO easier
> than bothering with low-level ATA commands.
Good advice, though I have to find the XFS equivalent.
Still: I wonder if the occasional bad sector is really that bad.
Shirley, at the unreal densities of today's drives, the development of
bad sectors is inevitable? (Especially in a laptop drive that's
bounced around in normal use.)
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
next prev parent reply other threads:[~2004-02-16 3:37 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 [this message]
2004-02-16 3:47 ` Jeff Garzik
2004-02-16 3:58 ` Valdis.Kletnieks
2004-02-16 4:09 ` Jeff Garzik
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=20040216033740.GE3789@perlsupport.com \
--to=chip@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jgarzik@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.