From: chuck <chuck@gelm.net>
To: patrick.gelin@free.fr
Cc: linux-admin@vger.kernel.org
Subject: Re: Badblocs too long...
Date: Thu, 22 Jan 2004 16:24:35 -0500 [thread overview]
Message-ID: <40103F93.646DC2C8@gelm.net> (raw)
In-Reply-To: bumbpa$dkd$1@sea.gmane.org
Hi, Patrick:
I tested my badblocks (from E2fsprogs 1.22) on a
Slackware 8.0 distribution using kernel 2.4.19 and when I
'badblocks -v -n /dev/hdb1'
the following three lines appear immediately:
Initializing random test data
Checking for bad blocks in non-destructive read-write mode
From block 0 to 8225248
A portion of 'man badblocks' returns:
-n Use non-destructive read-write mode. By default
only a non-destructive read-only test is done.
This option must not be combined with the -w
option, as they are mutually exclusive.
-v Verbose mode.
What EXACTLY happens when you do the same?
Perhaps
HTH, Chuck
Patrick Gelin wrote:
>
> chuck gelm net wrote:
>
> > Try:
> >
> > badblocks -v -n /dev/hdb1
> >
> I tried, but it asked me a random patern, I don't know what to do, neither
> how to leave...
>
> Moreover, man documentation explein it's longer with -n option...
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-01-22 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 21:10 Badblocs too long Patrick Gelin
2004-01-21 1:35 ` Axel Siebenwirth
2004-01-21 17:18 ` Patrick Gelin
2004-01-21 1:48 ` chuck gelm net
2004-01-21 17:15 ` Patrick Gelin
2004-01-22 21:24 ` chuck [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 17:34 Carrión Byron
2004-01-21 18:16 ` Patrick Gelin
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=40103F93.646DC2C8@gelm.net \
--to=chuck@gelm.net \
--cc=linux-admin@vger.kernel.org \
--cc=patrick.gelin@free.fr \
/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.