From: Vitaly Fertman <vitaly@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: serge rossel <serger@rocketmail.com>, reiserfs-list@namesys.com
Subject: Re: bug report (?) with reiserfsck --rebuild-tree.......
Date: Sat, 10 May 2003 21:14:20 +0400 [thread overview]
Message-ID: <200305102114.20627.vitaly@namesys.com> (raw)
In-Reply-To: <3EBD2976.2080406@namesys.com>
On Saturday 10 May 2003 20:31, Hans Reiser wrote:
> Vitaly, does the current fsck explain at length that read errors tend to
> be hardware failures, and what to do?
yes, it sais
The problem has occurred looks like a hardware problem.
If you have bad blocks, we advise you to get a new hard
drive, because once you get one bad block that the disk
drive internals cannot hide from your sight, the chances
of getting more are generally said to become much higher
(precise statistics are unknown to us), and this disk drive
is probably not expensive enough for you to risk your time
and data on it. If you don't want to follow that advice,
then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that
means it takes a block it has in reserve and allocates it
for use for requests of that block number). If it cannot
remap the block, this could be quite bad, as it may mean
that so many blocks have gone bad that none remain in
reserve to allocate.
> >SeekComplete DataRequest Error }
> ><4>hda: read_intr: error=0x40 { UncorrectableError },
> >LBAsect=230962500, sector=188743680
> ><4>end_request: I/O error, dev 03:04 (hda), sector
> >188743680
> ><4>sh-2029: reiserfs read_bitmaps: bitmap block
> >(#23592960) reading failed
> ><4>sh-2014: reiserfs_read_super: unable to read bitmap
> ><4>hda: read_intr: status=0x59 { DriveReady
> >SeekComplete DataRequest Error }
> ><4>hda: read_intr: error=0x40 { UncorrectableError },
> >LBAsect=231224644, sector=189005824
> ><4>end_request: I/O error, dev 03:04 (hda), sector
> >189005824
> ><4>hda: read_intr: status=0x59 { DriveReady
> >SeekComplete DataRequest Error }
> ><4>hda: read_intr: error=0x40 { UncorrectableError },
> >LBAsect=231486789, sector=189267968
> ><4>end_request: I/O error, dev 03:04 (hda), sector
this is a hadrware problem.
> >serge@dhcppc2:~> su
> >Password:
> >dhcppc2:/home/serge # reiserfsck --rebuild-tree
> >--logfile check.log /var/log
> >reiserfsck 3.6.2 (2002)
> >
> >Will rebuild the filesystem (/var/log) tree
> >Will put log info to 'check.log'
> >
> >Do you want to run this program?[N/Yes] (note need to
> >type Yes):Yes
> >
> >bread: Cannot read a block # 2.
> >
> >Abandon
Serge, if you used the latest reiserfsprogs, you would get
the message above.
--
Thanks,
Vitaly Fertman
prev parent reply other threads:[~2003-05-10 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 14:51 bug report (?) with reiserfsck --rebuild-tree serge rossel
2003-05-10 16:31 ` Hans Reiser
2003-05-10 17:14 ` Vitaly Fertman [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=200305102114.20627.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=serger@rocketmail.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.