From: Szakacsits Szabolcs <szaka@sienet.hu>
To: "Rudy L. Zijlstra" <rudy@edsons.demon.nl>
Cc: Whit Blauvelt <whit@transpect.com>, reiserfs-list@namesys.com
Subject: Re: Marking bad blocks
Date: Mon, 21 Jul 2003 00:59:08 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.30.0307210002150.22903-100000@divine.city.tvnet.hu> (raw)
In-Reply-To: <3F1A5E0E.6070505@edsons.demon.nl>
On Sun, 20 Jul 2003, Rudy L. Zijlstra wrote:
> In my experience, you are courting a great amount of data loss.
Considering Whit's disk is old and the bad sectors are new, quite probably.
[... nice harddisk history summary ...]
I've believed the same on the current state. Until I wrote ntfsresize and
it started its life one year ago. I marked 'bad block handling' the lowest
priority but never really planned to implement it, you explained why. NTFS
keeps a list of bad sectors and ntfsresize only checks its presence and
refuses to make the modifications if the disk is "dying".
The problem, it appears there is a decent number of disks leaving the
factories nowaday already having bad sectors (in short, no hidden cylinders
or they are full). Users claim disk remains stable, no new bad sectors with
time and most of them aren't even willing to replace it. Just like in the
early 80's. So in the end, I "had to" write the code.
Szaka
next prev parent reply other threads:[~2003-07-20 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 3:30 Marking bad blocks Whit Blauvelt
2003-07-20 9:17 ` Rudy L. Zijlstra
2003-07-20 22:59 ` Szakacsits Szabolcs [this message]
2003-07-20 10:39 ` Vitaly Fertman
2003-07-20 14:23 ` Whit Blauvelt
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.30.0307210002150.22903-100000@divine.city.tvnet.hu \
--to=szaka@sienet.hu \
--cc=reiserfs-list@namesys.com \
--cc=rudy@edsons.demon.nl \
--cc=whit@transpect.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 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.