From: "Peter" <sw98234-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org
Subject: Re: FEATURE Req: integrate badblocks check into fsck.reiser*
Date: Fri, 1 Sep 2006 23:02:57 +0000 (UTC) [thread overview]
Message-ID: <edae71$iqf$1@sea.gmane.org> (raw)
In-Reply-To: 44F8B3C8.1050802@slaphack.com
On Fri, 01 Sep 2006 17:27:20 -0500, David Masover wrote:
snip...
>> both mkfs.reiserfs and fsck.reiserfs have -B option to accept list of
>> bad blocks. We thought that should be enough.
>
> It really should. Why bother with a patch? Just write a wrapper script
> that runs badblocks and passes in the list to mkfs.
It was just a thought from userland. My perspective was that a user, not a
hard-boiled geek, might get lulled into a false sense of security but may
not have the wherewithal to write a wrapper. If nothing else, when the
final doc is written (did I say final?:)), it should include a notice
about not running badblocks.
--
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via
jabber: pete4abw at jabber.org
ICQ: 73676357
next prev parent reply other threads:[~2006-09-01 23:02 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
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 [this message]
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='edae71$iqf$1@sea.gmane.org' \
--to=sw98234-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
--cc=reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org \
/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.