mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: monkeyiq <monkeyiq@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dying disk and filesystem choice.
Date: Thu, 24 May 2001 00:58:14 -0600 (MDT)	[thread overview]
Message-ID: <200105240658.f4O6wEWq031945@webber.adilger.int> (raw)
In-Reply-To: <m3bsoj2zsw.fsf@kloof.cr.au> "from monkeyiq at May 24, 2001 01:25:51 pm"

It was written:
>   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.

Well reiserfs is probably a very bad choice at this point.  It
does not have any bad blocks support (yet), so as soon as you have
a bad block you are stuck.

You should probably use ext2, along with the badblocks program to
check which blocks in the disk are bad.  It will do a read-write
test, and either your disk will remap the bad blocks, or they will
be detected.

Even so, keep your backups current...

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  parent reply	other threads:[~2001-05-24  7:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24  3:25 monkeyiq
2001-05-24  6:03 ` Hans Reiser
2001-05-24  6:58 ` Andreas Dilger [this message]
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 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
2001-05-24 15:50   ` Jonathan Lundell
2001-05-24 15:56     ` Andi Kleen
2001-05-24 16:13     ` Jonathan Lundell
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=200105240658.f4O6wEWq031945@webber.adilger.int \
    --to=adilger@turbolinux.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

all inboxes | Powered by JetHome®