From: Pavel Machek <pavel@ucw.cz>
To: "Theodore Ts'o" <tytso@mit.edu>, Andrew Morton <akpm@digeo.com>,
Ross Biro <rossb@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] Failed writes marked clean?
Date: Tue, 12 Nov 2002 21:04:28 +0100 [thread overview]
Message-ID: <20021112200421.GC861@zaurus> (raw)
In-Reply-To: <20021108233530.GA23888@think.thunk.org>
Hi!
> In some circumstances, it may actually make sense to try writing a
> random block of data to the disk, since that may force the disk to
> remap the block. (Disks generally only remap a block from the pool of
> spare blocks on writes, not on reads.)
>
> Unfortuantely, if the error was just a transient one, you might end up
> smashing the block when you write random garbage in an attempt to
> remap the block. So perhaps the answer is to retry the read, and if
> that fails, *then* try to do a forced rewrite of the block.
>
Retrying is not enough. I've seen a notebook
overheating: its cpu was still okay but HDD
was too hot and started acting crazy. I got
away with 2 bad blocks and FS survived. If
kernel tried to do something clever it would
probably make corruption much worse.
Pavel
--
Pavel
My velo broke, so I got Zaurus. If you have Philips Velo 1 you don't need...
prev parent reply other threads:[~2002-11-15 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 20:29 [BUG] Failed writes marked clean? Ross Biro
2002-11-08 20:53 ` Linus Torvalds
2002-11-08 20:57 ` Andrew Morton
2002-11-08 21:30 ` Ross Biro
2002-11-08 23:35 ` Theodore Ts'o
2002-11-09 1:29 ` Bernd Eckenfels
2002-11-12 20:04 ` Pavel Machek [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=20021112200421.GC861@zaurus \
--to=pavel@ucw.cz \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rossb@google.com \
--cc=tytso@mit.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