From: Oleg Drokin <green@namesys.com>
To: Peter Lojkin <ia6432@inbox.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre3 and reiserfs problem (not boot)
Date: Fri, 11 Jul 2003 19:49:59 +0400 [thread overview]
Message-ID: <20030711154959.GJ17180@namesys.com> (raw)
In-Reply-To: <E19b019-000Grz-00.ia6432-inbox-ru@f25.mail.ru>
Hello!
On Fri, Jul 11, 2003 at 07:41:03PM +0400, "Peter Lojkin" wrote:
> > There was one more reiserfs message in kernel log just before this
> > line, can you please include it?
> right. ksymoops cut it out so i missed it.
> Jul 10 06:25:10 host kernel: journal-601, buffer write failed
Well, the write to journal failed. Reiserfs panics in such an event as it does not
know what to do in such a case (there are some works at SuSE by Jeff Mahoney to
remount r/o if such an event happens).
> another thing to note, both oopses happend exactly at 06:25:41 (Jul 10 and 11), and both times there were "journal-601, buffer write failed"
> close prior to it.
Well, how about some i/o error messages from block device drivers?
> in the logs we often get messages like:
> Jul 11 14:25:59 host kernel: (scsi0:A:10:0): parity error detected in Data-out phase. SEQADDR(0x55) SCSIRATE(0xc2)
> Jul 11 14:25:59 host kernel: ^INo terminal CRC packet recevied
Hm, can that lead to i/o error propagated up to reiserfs? If yes, then thats' the problem.
> _but_ with 2.4.21-rc? kernel it cause no problems and no data loss.
> promise box itself doesn't detect any errors.
> i've checked the list and found coule of messages about such "parity
> errors" in recent kernels, but no solution or any info about it
> causing problems.
> hoping to get rid of this messages i've tried 2.4.22-pre3 and got
> oopses...
Hm, I guess you need to stop the driver to propagate i/o errors upstream
(perhaps find a recent change that started to do this).
There is nothing to do from reiserfs perspective (except for better error handling,
which will not do you anything good anyway).
Bye,
Oleg
next prev parent reply other threads:[~2003-07-11 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 14:08 2.4.22-pre3 and reiserfs problem (not boot) "Peter Lojkin"
2003-07-11 14:29 ` Oleg Drokin
2003-07-11 15:41 ` Re[2]: " "Peter Lojkin"
2003-07-11 15:49 ` Oleg Drokin [this message]
2003-07-11 16:06 ` "Peter Lojkin"
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=20030711154959.GJ17180@namesys.com \
--to=green@namesys.com \
--cc=ia6432@inbox.ru \
--cc=linux-kernel@vger.kernel.org \
/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.