From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Hans Reiser '" <reiser@namesys.com>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
"'John Bradford '" <john@grabjohn.com>,
<linux-kernel@vger.kernel.org>, <nikita@namesys.com>,
"'Pavel Machek '" <pavel@ucw.cz>,
"'Justin Cormack '" <justin@street-vision.com>,
"'Russell King '" <rmk+lkml@arm.linux.org.uk>,
"'Vitaly Fertman '" <vitaly@namesys.com>,
"'Krzysztof Halasa '" <khc@pm.waw.pl>
Subject: Re: Blockbusting news, results end
Date: Sun, 26 Oct 2003 17:49:29 +0900 [thread overview]
Message-ID: <346101c39b9e$35932680$24ee4ca5@DIAMONDLX60> (raw)
The drive finally reallocated the block and there are no longer any visible
bad blocks.
I will not be able to perform the following planned test:
Well, in a future weekend, I will try to see if ext2fs really takes action
on permanently bad blocks that are detected during normal operations on a
mounted partition.
But I think the underlying defects remain in need of correction. Toshiba
knows about theirs but will probably never say if they make any fixes. Mr.
Reiser and friends have plans to add important features, and I am unable to
detect if ext2fs needs it. (As mentioned before, I understand that ext2fs
can do it during formatting and fsck, but no one seems to be saying what
happens if a permanently bad block is detected during normal operation on a
mounted partition.)
next reply other threads:[~2003-10-26 8:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 8:49 Norman Diamond [this message]
2003-10-26 9:22 ` Blockbusting news, results end Pavel Machek
2003-10-26 11:25 ` Norman Diamond
2003-10-27 20:58 ` jw schultz
2003-10-27 22:27 ` Andre Hedrick
2003-10-27 22:57 ` jw schultz
2003-10-28 2:03 ` jw schultz
2003-10-26 11:01 ` Hans Reiser
2003-10-26 12:59 ` Oleg Drokin
2003-10-26 12:05 ` Hans Reiser
2003-10-26 12:39 ` Oleg Drokin
2003-10-26 16:26 ` Hans Reiser
2003-10-26 17:13 ` Oleg Drokin
2003-10-26 18:20 ` Hans Reiser
2003-10-26 19:07 ` Oleg Drokin
2003-10-27 12:44 ` Vitaly Fertman
2003-10-26 18:39 Mudama, Eric
2003-10-27 9:45 ` Norman Diamond
2003-10-27 10:48 ` Krzysztof Halasa
2003-10-27 17:50 Mudama, Eric
2003-10-28 11:31 Norman Diamond
2003-10-28 16:10 Mudama, Eric
2003-10-28 18:30 ` bill davidsen
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='346101c39b9e$35932680$24ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=reiser@namesys.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@namesys.com \
/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).