From: Oleg Drokin <green@namesys.com>
To: Alexander Saers <alex@saers.com>
Cc: reiserfs-list@namesys.com
Subject: Re: bad blocks
Date: Mon, 17 Jun 2002 19:23:41 +0400 [thread overview]
Message-ID: <20020617192341.A31733@namesys.com> (raw)
In-Reply-To: <20020617171628.C74247-100000@doriath.saers.com>
Hello!
On Mon, Jun 17, 2002 at 05:19:18PM +0200, Alexander Saers wrote:
> But this only makes the sectors busy and the next reiserfsck will then
> detect this and remove the bussy mark. Isnt there a way to create files on
> the bad sectors so that nobody uses them. Not even in the future after a
> reiserfsck. Like if i have a folder on the drive that says
> /badblocks/sector8004
> /badblocks/sector8010
> etc etc
> Thanx fo a good filesystem
New reiserfsck have support for lists of bad blocks, but this was not
strongly tested and therefore disabled by default.
But some work is done in this direction
Bye,
Oleg
next prev parent reply other threads:[~2002-06-17 15:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 15:19 bad blocks Alexander Saers
2002-06-17 15:23 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-20 18:55 Bad Blocks Dyweni - Ceph-Devel
2013-03-28 15:54 ` Gregory Farnum
2005-04-26 20:33 Eddie Dawydiuk
2005-04-26 22:43 ` Charles Manning
2005-02-17 7:14 Question regarding mdadm.conf Michael Tokarev
2005-02-17 8:30 ` Bad blocks Guy
2004-04-01 14:06 Kalev Lember
2004-04-01 14:36 ` David Woodhouse
2004-04-02 0:14 ` Greg Ungerer
2004-04-04 11:16 ` Kalev Lember
2002-09-24 7:54 Bad Blocks Aleksander Kujbida
2002-09-24 4:14 Aleksander Kujbida
2002-09-24 4:54 ` Glynn Clements
2002-09-23 14:17 Abiy,Mike [Edm]
2002-09-23 20:33 ` Glynn Clements
[not found] <F8500ECEBD66D211A3D20008C724A29C01CEFD9D@SR-EDM-EXCH4.edm. ab.ec.gc.ca>
2002-09-19 15:03 ` Scott Taylor
2002-09-19 14:48 Abiy,Mike [Edm]
2002-09-19 15:23 ` Jorge R . Csapo
2002-04-16 1:13 Bad blocks Sam Vilain
2002-04-16 11:43 ` Matthias Andree
2002-04-16 11:47 ` Oleg Drokin
2002-04-16 12:01 ` Ed Tomlinson
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=20020617192341.A31733@namesys.com \
--to=green@namesys.com \
--cc=alex@saers.com \
--cc=reiserfs-list@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 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.