From: Oleg Drokin <green@linuxhacker.ru>
To: ndiamond@wta.att.ne.jp, vitaly@namesys.com,
linux-kernel@vger.kernel.org, reiser@namesys.com
Subject: Re: Blockbusting news, results end
Date: Sun, 26 Oct 2003 14:59:43 +0200 [thread overview]
Message-ID: <200310261259.h9QCxhWv004314@car.linuxhacker.ru> (raw)
In-Reply-To: 3F9BA98B.20408@namesys.com
Hans Reiser <reiser@namesys.com> wrote:
HR> Badblocks support is in reiser4, and anyone is welcome to update the
HR> patch for V3, or sponsor us to do it. We are very low on cash, so we
Actually that v3 patch does not do bad blocks remapping in case of
write failure, it only does remapping when you manually ask it.
And biggest part of badblocks support in reiser3 is in reiserfsck and tools
(and in not that bad shape, last time I looked).
As for remapping bad blocks on write failure, the only PC OS that was doing
this that comes to my mind is Novell Netware (I think they called it a "hotfix"
or something like that).
Bye,
Oleg
next prev parent reply other threads:[~2003-10-26 11:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 8:49 Blockbusting news, results end Norman Diamond
2003-10-26 9:22 ` 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 [this message]
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=200310261259.h9QCxhWv004314@car.linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--cc=reiser@namesys.com \
--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).