All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: reiserfs-list@namesys.com
Cc: Peter <sw98234@hotmail.com>
Subject: Re: FEATURE Req: integrate badblocks check into fsck.reiser*
Date: Fri, 1 Sep 2006 22:50:44 +0400	[thread overview]
Message-ID: <200609012250.44548.vs@namesys.com> (raw)
In-Reply-To: <ed9tqo$2tc$1@sea.gmane.org>

Hello

On Friday 01 September 2006 22:23, Peter wrote:
> Perhaps this has been mentioned before. If so, sorry. IMHO, it would be
> useful to integrate a call to badblocks in the fsck/mkfs.reiser* programs
> so that more thorough disk checking can be done at format time. Sort of
> like the option e2fsck -c. If this is added, the output could be fed
> immediately to the reiser format program and badblocks spared prior to
> filesystem use.
>
> JM$0.02

both mkfs.reiserfs and fsck.reiserfs have -B option to accept list of bad 
blocks. We thought that should be enough.

  reply	other threads:[~2006-09-01 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 18:23 FEATURE Req: integrate badblocks check into fsck.reiser* Peter
2006-09-01 18:50 ` Vladimir V. Saveliev [this message]
2006-09-01 19:26   ` Hans Reiser
2006-09-01 22:27   ` David Masover
2006-09-01 23:00     ` Hans Reiser
2006-09-01 23:02     ` Peter
2006-09-01 23:12       ` David Masover
2006-09-01 23:16         ` Hans Reiser
2006-09-04  2:41         ` Ric Wheeler
2006-09-06  0:53           ` Hans Reiser
2006-09-06 15:08             ` David Masover
2006-09-07 10:35               ` Ric Wheeler
2006-09-07 16:22                 ` David Masover
2006-09-07 17:10                   ` Ric Wheeler
2006-09-07 17:35                     ` David Masover
2006-09-08 12:29                       ` Peter

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=200609012250.44548.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sw98234@hotmail.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.