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, 8 Sep 2006 12:29:51 +0000 (UTC) [thread overview]
Message-ID: <edrnnv$n1m$1@sea.gmane.org> (raw)
In-Reply-To: 4500584A.4040601@slaphack.com
On Thu, 07 Sep 2006 12:35:06 -0500, David Masover wrote:
all snip.....
All I was getting at originally was to make fsck.reiser4 behave similarly
to other fsck/mkfs programs so that it _could_, when requested, check a
disk/partition for bad blocks. Despite the improved capabilities of modern
drives, sh*t happens. And I, for one, would like the option of knowing
before formatting a new partition if it's OK to do so. Sure, I can run
badblocks myself, but this is counter to what I do with other fsck
programs.
A wrapper script would work fine, and I suppose, some sort of pipe output.
However, I'm just looking at this from a userland perspective, not that of
a sysadmin. Obviously, a sysadmin would not put any disk into production
that has not been carefully tested.
If this is superfluous, that's OK. I can easily work around it, but it
should be noted somewhere in a README that reiserfs/4 does not do bad
block checking during format and only a quick format is done.
--
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
prev parent reply other threads:[~2006-09-08 12:29 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
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 [this message]
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='edrnnv$n1m$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.