From: Kuba Ober <kuba@mareimbrium.org>
To: Andreas Abele <aba@IZS.FhG.de>
Cc: reiserfs-list@namesys.com
Subject: Re: mkreiserfs and big RAID-Systems
Date: Mon, 15 Jul 2002 12:46:48 -0400 [thread overview]
Message-ID: <200207151246.48372.kuba@mareimbrium.org> (raw)
In-Reply-To: <1026757533.32136.26.camel@pallas.IZS.FhG.de>
> > > Jul 16 01:26:39 saturn6 kernel: I/O error: dev 08:51, sector 1680768424
> > This is likely to be a bad block. Run
> > /sbin/badblock -b 4096 /dev/sdf1 210096053 210096053
> > or with some range.
> i tried the command
You couldn't. It should be badblocks, not badblock (or did you catch that?)
> but if i am right, i have to declare 120 G-Blocks
> as bad
You are not right. Read
man badblocks
first, so that you have idea of what you're doing. The numbers (210096053)
specify a range of 4096 byte long blocks to test.
He advised you to *test* reading from the supposedly bad block first, and
that's why you should call badblocks on that block.
The thing is that the kernel has problems reading a block from your raid
array:
> > > Jul 16 01:26:39 saturn6 kernel: I/O error: dev 08:51, sector 1680768424
Fix that first. This has nothing to do with reiserfs -- reiserfs won't help if
kernel cannot read a block from the device.
Cheers, Kuba Ober
next prev parent reply other threads:[~2002-07-15 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 13:59 mkreiserfs and big RAID-Systems Andreas Abele
2002-07-15 12:39 ` Vitaly Fertman
2002-07-15 14:55 ` Andreas Abele
2002-07-15 13:38 ` Vitaly Fertman
2002-07-15 16:01 ` Andreas Abele
2002-07-15 14:24 ` Vitaly Fertman
2002-07-15 16:42 ` Andreas Abele
2002-07-15 16:08 ` Vitaly Fertman
2002-07-15 18:25 ` Andreas Abele
2002-07-15 16:41 ` Vitaly Fertman
2002-07-15 16:46 ` Kuba Ober [this message]
2002-07-15 16:53 ` Kuba Ober
2002-07-15 15:47 ` Alexander Saers
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=200207151246.48372.kuba@mareimbrium.org \
--to=kuba@mareimbrium.org \
--cc=aba@IZS.FhG.de \
--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.