From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: "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>
Subject: Re: Blockbusting news, results are in
Date: 19 Oct 2003 17:55:09 +0200 [thread overview]
Message-ID: <m34qy5ql2a.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <021501c39618$615619c0$24ee4ca5@DIAMONDLX60>
"Norman Diamond" <ndiamond@wta.att.ne.jp> writes:
> 3. If there were a way to enable reallocation in case of permanent errors,
> I think my friends would have said. But they sure didn't say there were any
> user-settable options, they only said some approximations of how it was
> designed.
Other drives remap on write by default.
> It does reallocations after temporary read errors but not after
> permanent read errors (where permanent means 255 failures in auto-retry).
Good so far.
> They think it does reallocations after temporary write errors, they weren't
> sure if it does reallocations after permanent write errors, now we know that
> it doesn't do reallocations after permanent write errors, and this is how it
> is designed, with no hint of options to toggle.
There isn't (shoudn't be) such a thing as "temporary" or "permanent"
write error. A write error should cause a sector to be remapped (the
question about how many times the drive should try to write a single
sector is irrelevant here). The drive should not return write error
unless all spare sectors are already in use (which means the drive
is approaching death and should be replaced immediately).
All drives I currently use do just that (though I don't currently use
Toshiba drives).
I would rather ask Toshiba if it's a bug in their firmware and if they
have fixed it. Or buy another brand.
> Why does RAM carry 6 year warranties? (Maybe some don't but this is
> common.)
It doesn't have moving parts.
> > BTW, you're welcome to buy "premium" drives with 3-year or 5-year
> > warranties. (3 on most vendor's high end ATA products, and 5 years on
> > most SCSI products)
We have that here (ATA, and I think all SCSI drives have 5 years).
Not sure about exact price increase, though.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2003-10-19 15:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 15:18 Norman Diamond
2003-10-21 19:31 ` Chuck Campbell
2003-10-21 20:05 ` Richard B. Johnson
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
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 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=m34qy5ql2a.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--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
all inboxes | Powered by JetHome®