From: Hans Reiser <reiser@namesys.com>
To: monkeyiq <monkeyiq@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dying disk and filesystem choice.
Date: Wed, 23 May 2001 23:03:20 -0700 [thread overview]
Message-ID: <3B0CA428.82447AA2@namesys.com> (raw)
In-Reply-To: <m3bsoj2zsw.fsf@kloof.cr.au>
monkeyiq wrote:
>
> Hi,
> Could I please be CC'd replies.
>
> To keep it short and sweet, I have a 45Gb IBM drive that
> is slowly dying by getting more bad sectors. I have already
> returned my first one to get the current disk, so would like
> to use the current one for a while before returning it for
> another disk that will prolly just start dying again.
>
> I am using reiserfs at the moment, which doesn't really like
> to work on a dying drive. for example, doing a make fails to
> work even though it is *creating* files on the disk, it fails
> to do so because it hits new bad sectors and doesn't seem to
> remap them.
>
> I am wondering what advise on filesystem choice the list as
> and any other options I can use to get the kernel to remap
> bad blocks.
>
> Thanks.
>
> --
> ---------------------------------------------------
> It's the question, http://witme.sourceforge.net
> If you think education is expensive, try ignorance.
> -- Derek Bok, president of Harvard
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
You can get the badblocks patch from Nikita and continue using reiserfs if you
want. ext2 will also work.
We haven't sent the badblocks patch to Linus solely because it is a feature not
a bugfix, and code-freeze is on.
Hans
next prev parent reply other threads:[~2001-05-24 6:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 3:25 Dying disk and filesystem choice monkeyiq
2001-05-24 6:03 ` Hans Reiser [this message]
2001-05-24 6:58 ` Andreas Dilger
2001-05-24 8:31 ` Andi Kleen
2001-05-24 10:19 ` Jens Axboe
2001-05-24 12:08 ` monkeyiq
2001-05-24 15:46 ` Jonathan Lundell
2001-05-24 15:50 ` Jonathan Lundell
2001-05-24 15:56 ` Andi Kleen
2001-05-24 16:13 ` Jonathan Lundell
2001-05-24 16:53 ` Hans Reiser
2001-05-24 17:16 ` David Rees
2001-05-24 19:03 ` J Sloan
2001-05-24 20:54 ` Hans Reiser
2001-05-24 19:46 ` Erik Mouw
2001-05-24 21:24 ` Hans Reiser
2001-05-24 22:16 ` Alan Cox
2001-05-25 13:21 ` Chris Mason
2001-05-25 16:21 ` Hans Reiser
2001-05-25 16:58 ` Chris Mason
2001-05-25 17:42 ` Hans Reiser
2001-05-25 11:29 ` Juan Quintela
2001-05-24 21:35 ` monkeyiq
-- strict thread matches above, loose matches on Subject: below --
2001-05-24 17:30 Cress, Andrew R
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=3B0CA428.82447AA2@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monkeyiq@users.sourceforge.net \
/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