From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Chuck Campbell <campbell@accelinc.com>
Cc: Norman Diamond <ndiamond@wta.att.ne.jp>, linux-kernel@vger.kernel.org
Subject: Re: Blockbusting news, results are in
Date: Tue, 21 Oct 2003 16:05:15 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0310211558500.19942@chaos> (raw)
In-Reply-To: <20031021193128.GA18618@helium.inexs.com>
On Tue, 21 Oct 2003, Chuck Campbell wrote:
> On Wed, Oct 22, 2003 at 12:18:33AM +0900, Norman Diamond wrote:
> > It still seems that either Linux must
> > be made to work around known bad blocks or else hard disks and Linux cannot
> > be used together on a computer.
>
> That is a bit of a troll. I suspect that 70 - 90 percent of linux
> installations on a computer are using hard disks. Yet the number of people
> having the same problem as you doesn't appear to be 100% of those.
>
> Making intentionally inflammatory statements to try and win others to your
> point of view tends to do exactly the opposite.
>
> If there are enough people experiencing the problem, it gets fixed, at least
> as far as I can tell. There have been a nunmber of viable ideas proposed
> in this thread to handle the situation you are talking about, and while
> none of them are exactly what you proposed, feel free to write code. Baiting
> comments like the above don't really accomplish anything constructive.
>
> -chuck
I thought both ext2 and ext3 do handle bad-blocks. They just
don't make them owned by a "file" because the Unix file-systems
don't require dummy directory entries.
If the respondent wants them isolated into a "BADBLOCKS" file,
he can make a utility to do that. It's really quite easy because
you can raw-read disks under Linux, plus there is already
the `badblocks` program that will locate them.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-10-21 20:02 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 15:18 Norman Diamond
2003-10-21 19:31 ` Chuck Campbell
2003-10-21 20:05 ` Richard B. Johnson [this message]
2003-10-21 20:21 ` Valdis.Kletnieks
2003-10-21 20:31 ` Richard B. Johnson
2003-10-21 21:53 ` Theodore Ts'o
2003-10-22 2:32 ` Valdis.Kletnieks
2003-10-23 17:28 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 15:55 Mudama, Eric
2003-10-20 17:32 ` Hans Reiser
2003-10-20 14:08 Mudama, Eric
2003-10-20 14:42 ` John Bradford
2003-10-19 17:51 Mudama, Eric
2003-10-20 6:22 ` Rogier Wolff
2003-10-19 17:39 Mudama, Eric
2003-10-19 17:36 Mudama, Eric
2003-10-19 7:37 Mudama, Eric
2003-10-19 8:09 ` Norman Diamond
2003-10-19 8:24 ` Hans Reiser
2003-10-19 11:43 ` Ralf Baechle
2003-10-19 15:55 ` Krzysztof Halasa
2003-10-19 8:13 ` Rogier Wolff
2003-10-19 8:17 ` Hans Reiser
2003-10-19 8:41 ` Rogier Wolff
2003-10-20 15:56 ` Thayne Harbaugh
2003-10-19 8:21 ` Andre Hedrick
2003-10-19 8:27 ` Hans Reiser
2003-10-19 9:01 ` Erik Andersen
2003-10-19 14:10 ` Andre Hedrick
2003-10-19 18:16 ` Hans Reiser
2003-10-19 19:44 ` Andre Hedrick
2003-10-20 7:21 ` Hans Reiser
2003-10-19 14:42 ` Valdis.Kletnieks
2003-10-19 10:47 ` Ingo Oeser
2003-10-19 2:16 Norman Diamond
2003-10-19 4:15 ` Larry McVoy
2003-10-19 5:00 ` Paul
2003-10-19 8:19 ` Andre Hedrick
2003-10-19 8:08 ` Hans Reiser
2003-10-19 8:35 ` William Lee Irwin III
2003-10-19 20:01 ` Pavel Machek
2003-10-19 20:11 ` William Lee Irwin III
2003-10-20 7:24 ` John Bradford
2003-10-19 22:49 ` jw schultz
2003-10-20 7:22 ` John Bradford
2003-10-20 8:22 ` jw schultz
2003-10-20 7:27 ` Hans Reiser
2003-10-20 8:08 ` jw schultz
2003-10-19 19:49 ` Pavel Machek
2003-10-20 7:22 ` Hans Reiser
2003-10-21 10:31 ` Eric W. Biederman
2003-10-21 8:43 ` Jan-Benedict Glaw
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=Pine.LNX.4.53.0310211558500.19942@chaos \
--to=root@chaos.analogic.com \
--cc=campbell@accelinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/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
all inboxes | Powered by JetHome®