From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@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 20:31:50 +0400 [thread overview]
Message-ID: <3EBD2976.2080406@namesys.com> (raw)
In-Reply-To: <20030510145146.58538.qmail@web13901.mail.yahoo.com>
Vitaly, does the current fsck explain at length that read errors tend to
be hardware failures, and what to do?
Hans
serge rossel wrote:
>Hi,
>
>During the system boot (Suse8.1), I get this
>boot_log.msg:
>
>
>dd: no flushcache support
><6>scsi0 : SCSI host adapter emulation for IDE ATAPI
>devices
><4> Vendor: JLMS Model: XJ-HD166S Rev:
>DS0F
><4> Type: CD-ROM ANSI
>SCSI revision: 02
><4> Vendor: SONY Model: CD-RW CRX175A Rev:
>1.0h
><4> Type: CD-ROM ANSI
>SCSI revision: 02
><7>sd_attach()
><7>sd_attach()
><4>reiserfs: found format "3.6" with standard journal
><4>reiserfs: checking transaction log (ide0(3,2)) for
>(ide0(3,2))
><4>reiserfs: using ordered data mode
><4>Using r5 hash to sort names
><4>VFS: Mounted root (reiserfs filesystem) readonly.
><5>Trying to move old root to /initrd ... failed
><5>Unmounting old root
><5>Trying to free ramdisk memory ... okay
><6>Freeing unused kernel memory: 164k freed
><6>md: Autodetecting RAID arrays.
><6>md: autorun ...
><6>md: ... autorun DONE.
><6>LVM version 1.0.5(mp-v6)(15/07/2002) module loaded
><6>Adding Swap: 136544k swap-space (priority 42)
><4>reiserfs: found format "3.6" with standard journal
><4>hda: read_intr: status=0x59 { DriveReady
>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
>189267968
>Kernel logging (ksyslog) stopped.
>Kernel log daemon terminating.
>
>
>Then, in order to solve that, I have tried all the
>different commands proposed with reiserfsck.
>
>Look what message I get by using this command.
>
>Thank you for your support
>Serge
>
>
>serge@dhcppc2:~> su
>Password:
>dhcppc2:/home/serge # reiserfsck --rebuild-tree
>--logfile check.log /var/log
>reiserfsck 3.6.2 (2002)
>
>**********************************************************
> ** This is an experimental version of
>reiserfsck,
>****!! MAKE A BACKUP FIRST !! **** Don't run this
>program unless something is broken. **
> ** Some types of random FS damage can be recovered
>from ** ** by this program, which basically
>throws away ** ** the internal nodes of the tree and
>then reconstructs ** ** them. This program is for use
>only by the desperate, ** ** and is of only beta
>quality. If you are using the ** ** latest
>reiserfsprogs and it fails please email ** ** bug
>reports to reiserfs-list@namesys.com.**
>
>**********************************************************
>
>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
>
>dhcppc2:/home/serge #
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Search - Faster. Easier. Bingo.
>http://search.yahoo.com
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-05-10 16:31 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 [this message]
2003-05-10 17:14 ` Vitaly Fertman
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=3EBD2976.2080406@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=serger@rocketmail.com \
--cc=vitaly@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.