From: Brian Marr <cabernet@internode.on.net>
To: Reiserfs list <reiserfs-list@namesys.com>
Subject: Re: Filesystem errors
Date: Tue, 16 Jul 2002 02:22:50 +0930 [thread overview]
Message-ID: <200207160222.50147.cabernet@internode.on.net> (raw)
In-Reply-To: <3D326683.1000606@namesys.com>
What reiserfsck paramaters should I try ? Do I have to do --rebuild-tree ?
Brian Marr
On Monday 15 July 2002 15:36, you wrote:
> Brian Marr wrote:
> >Can anyone help interpret these logs ? They have just started appearing on
> > my Suse 8.0 system. I have made some tentative exploration with
> > reiserfsck --check. The results were
> >reiserfsck......check started on Mon
> >Replaying journal
> >0 transactions replayed
> >checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
> >pass_through_tree: Unable to read block 52842 block on device 0x3
> >
> >The system is working but something is obviously wrong. Also the xserver
> > is taking ages to start.
>
> Probably you have bad blocks on your reiserfs partition. And because of
> this your xserver starts so slowly. Kernel trying to reread a block and
> can't do it, because it is bad.
>
> >Brian Marr
> >
> >(snip)==========
> >VFS: Disk change detected on device sr(11,0)
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >sector=422736
> >end_request: I/O error, dev 03:02 (hda), sector 422736
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >sector=422736
> >end_request: I/O error, dev 03:02 (hda), sec
> >
> >
> >(snip)======
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244,
> >sector=409984
> >end_request: I/O error, dev 03:02 (hda), sector 409984
> >vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
> > data of [96126 168017 0x0 SD]
next prev parent reply other threads:[~2002-07-15 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 16:16 Filesystem errors Brian Marr
2002-07-15 6:04 ` Robert Brockway
2002-07-15 6:20 ` Hans Reiser
2002-07-15 6:20 ` Hans Reiser
[not found] ` <3D326683.1000606@namesys.com>
2002-07-15 16:52 ` Brian Marr [this message]
[not found] ` <3D3268FF.5040505@namesys.com>
2002-07-15 18:07 ` Brian Marr
2002-07-17 5:42 ` Oleg Drokin
2002-07-17 8:06 ` Brian Marr
2002-07-17 8:10 ` Oleg Drokin
2002-07-17 12:11 ` Kuba Ober
2002-07-17 12:16 ` Oleg Drokin
2002-07-17 12:40 ` Kuba Ober
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=200207160222.50147.cabernet@internode.on.net \
--to=cabernet@internode.on.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.