From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: reiser@namesys.com (Hans Reiser)
Cc: nerijus@users.sourceforge.net (Nerijus Baliunas),
linux-kernel@vger.kernel.org (linux-kernel@vger.kernel.org)
Subject: Re: replaying reiserfs journal and bad blocks (was: Re[3]: Basic
Date: Fri, 7 Sep 2001 10:48:15 +0100 (BST) [thread overview]
Message-ID: <E15fIFE-0001JF-00@the-village.bc.nu> (raw)
In-Reply-To: <3B987D2A.41C975B3@namesys.com> from "Hans Reiser" at Sep 07, 2001 11:54:18 AM
> > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=84415, sector=36216
Thats the drive deciding it cant read the block.
> My guess is turn off UDMA, I think we have a www.namesys.com/faq.html entry on
> that which you can read and see if my memory of the typical symptoms of flaky
> udma are correct. Commenting on the cause of flaky udma I will leave to others
> familiar with your mob's interaction with Linux, except to say that one should> always check cables at a time like this.
You'd expect CRC errors then. It looks like the 2.2 log replay code worked
but the 2.4 log replay code failed on the error, or the layers below it in
the IDE got stuck.
next prev parent reply other threads:[~2001-09-07 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 13:00 Basic reiserfs question Mack Stevenson
2001-09-06 12:56 ` Hans Reiser
2001-09-06 14:09 ` Bob McElrath
2001-09-07 0:02 ` Re[2]: " Nerijus Baliunas
2001-09-07 0:22 ` replaying reiserfs journal and bad blocks (was: Re[3]: Basic reiserfs question) Nerijus Baliunas
2001-09-07 7:50 ` Basic reiserfs question Hans Reiser
2001-09-07 13:35 ` Re[2]: " Nerijus Baliunas
2001-09-09 10:10 ` Henning P. Schmiedehausen
2001-09-07 16:26 ` Nerijus Baliunas
[not found] ` <20010907002247.6A4418F703@mail.delfi.lt>
2001-09-07 7:54 ` replaying reiserfs journal and bad blocks (was: Re[3]: Basic reiserfs question) Hans Reiser
2001-09-07 9:48 ` Alan Cox [this message]
2001-09-06 22:38 ` Basic reiserfs question Chris Mason
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=E15fIFE-0001JF-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nerijus@users.sourceforge.net \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®