All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: ric@emc.com, Christian Kujau <lists@nerdbynature.de>,
	kgp <jyotiv@tataelxsi.co.in>,
	reiserfs-devel@vger.kernel.org
Subject: Re: bad block management
Date: Wed, 02 Apr 2008 02:11:18 +0400	[thread overview]
Message-ID: <47F2B306.6060202@gmail.com> (raw)
In-Reply-To: <47F29257.3000502@suse.com>

Jeff Mahoney wrote:

> Ric Wheeler wrote:
>
> >Christian Kujau wrote:
>
> >>On Mon, 31 Mar 2008, kgp wrote:
> >>
> >>>How ReiserFS manages bad blocks?
> >>
> >>Is reiserfsck's --badblocks option helpful?
> >>
> >>>If it is not supporting bad block management, plz tell me the
> >>>approches we
> >>>can use to implement bad block management in any file system. I am
> >>>implementing bad block manager for UDF. I want some inputs
> >>
> >>Doesn't "Spared UDF" already provide some kind of bad block management?
> >>
> >>C.
>
> >I am not sure what you want to do with bad block management.
>
> >With most modern disk drives, they will remap bad disk sectors
> >dynamically for you so the file system layer can stay out of the bad
> >block mapping business entirely.
>
>
> He's asking about UDF, though, so I'd imagine he's talking about optical
> media. It's even cheaper than disk though, so I guess I don't see the
> benefit.
>
> Reiserfs handles bad blocks by allocating the blocks input as "known
> bad" to special file that's inaccessible. It does _not_ do this
> automatically, and reiserfsck/mkreiserfs must be passed a list of blocks
> to allocate to that file. It also doesn't recover files that have been
> corrupted to the block failure.


Here are the instructions:
http://chichkin_i.zelnet.ru/bad-block-handling.html

>
> Ric's right about disk drives, though. They'll remap the bad sectors
> automatically at the hardware level. When you start to see bad sectors
> at the file system level, it means that the sectors reserved for
> remapping have been exhausted and you should replace the disk.
>
> -Jeff
>
> --
> Jeff Mahoney
> SUSE Labs

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2008-04-01 22:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  5:03 bad block management kgp
2008-04-01 18:55 ` Christian Kujau
2008-04-01 19:32   ` Ric Wheeler
2008-04-01 19:51     ` Jeff Mahoney
2008-04-01 22:11       ` Edward Shishkin [this message]
2008-04-02  4:50         ` jyotiv
2008-04-02 10:43           ` Ric Wheeler
2008-04-02 11:22             ` jyotiv
2008-04-02 13:31               ` Ric Wheeler
2008-04-02 13:14           ` Jeff Mahoney
2008-04-04  0:14       ` Zan Lynx
2008-04-04  4:21         ` Toby Thain
2008-04-04 16:12           ` Zan Lynx
2008-04-04 22:41             ` Toby Thain
2008-04-04 18:58           ` Ric Wheeler
2008-04-04 22:42             ` Toby Thain
2008-04-05 12:31               ` Ric Wheeler
2008-04-05 14:07                 ` Toby Thain
2008-04-05 15:08                   ` Ric Wheeler

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=47F2B306.6060202@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=jeffm@suse.com \
    --cc=jyotiv@tataelxsi.co.in \
    --cc=lists@nerdbynature.de \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=ric@emc.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.