All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Marius Reiner <news.mr@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: badblocks blocksize setting
Date: Sat, 15 Mar 2003 11:16:00 +0300	[thread overview]
Message-ID: <20030315111600.A24872@namesys.com> (raw)
In-Reply-To: <006b01c2ea87$20046a40$55c7a8c0@mariusw2k>

Hello!

On Sat, Mar 15, 2003 at 01:09:19AM +0100, Marius Reiner wrote:

> not really a reiserfs issue:
> When following the FAQ everything is fine, I set blocksize zu 4096 as
> debugreiserfs told me, and don't get any bad blocks.

Good.

> Nevertheless I'm a bit concerned about the ones, badblocks reports, when
> being invoked without the -b option. How does this happen?

Can you please show the command line and the resulting output with badblocks?
Also what is in dmesg output after such a run?

> Or should I just ignore them?

There is not enough info yet.
Can you please tell us whole story?

Bye,
    Oleg

  reply	other threads:[~2003-03-15  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-15  0:09 badblocks blocksize setting Marius Reiner
2003-03-15  8:16 ` Oleg Drokin [this message]
2003-03-15 11:38   ` Marius Reiner
2003-03-15 11:44     ` Oleg Drokin

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=20030315111600.A24872@namesys.com \
    --to=green@namesys.com \
    --cc=news.mr@gmx.net \
    --cc=reiserfs-list@namesys.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.