From: Oleg Drokin <green@namesys.com>
To: Weiping He <laser@zhengmai.com.cn>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: anybody know about "journal-615" and/or "journal-601" log error?
Date: Wed, 26 Dec 2001 09:42:09 +0300 [thread overview]
Message-ID: <20011226094209.B871@namesys.com> (raw)
In-Reply-To: <005401c18dc6$f3e3fb10$d20101c0@T21laser>
In-Reply-To: <005401c18dc6$f3e3fb10$d20101c0@T21laser>
Hello!
On Wed, Dec 26, 2001 at 12:36:18PM +0800, Weiping He wrote:
> but I've experienced server hang up of my box, the syslog entity is:
> (this show up after I re-compile the kernel with the reiserfs's:
> Have reiserfs do extra internal checking
> Stats in /proc/fs/reiserfs
> options set to enable)
> Dec 26 09:47:10 x200 kernel: journal-615: buffer write failed
> Dec 18 10:19:13 x200 kernel: journal-601, buffer write failed
Any other errors in the logs?
Reading the code these errors appear after we put IO request
and then watitng for it to be complete with wait_on_buffer().
But after wait_on_buffer returns, bufer is still not up to date,
which usually means IO request have failed for some reason.
> I've experienced power failure before the problem happens.
> and after it happens, in `top' I can see that `kupdated' mark as <debunc>
Yes, because there was an Oops after this message.
> my question is what's the matter here? I do some search in kernel archive
> but found almost nothing relate that 'journal-615' or 'journal-601'.
> Is it a bug or my sw/hw configure problem?
Right now it looks more like a HW problem.
Can you dig more messages from your kernel log.
Can you try to run reiserfsck on a problematic partition and see
if there is anything wrong?
Bye,
Oleg
next prev parent reply other threads:[~2001-12-26 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 4:36 anybody know about "journal-615" and/or "journal-601" log error? Weiping He
2001-12-26 6:42 ` Oleg Drokin [this message]
2001-12-26 8:38 ` Weiping He
2002-01-10 2:11 ` anybody know about "journal-615" and/or "journal-601" log error?(may be SCSI problem?) Weiping He
2002-01-10 10:21 ` Nikita Danilov
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=20011226094209.B871@namesys.com \
--to=green@namesys.com \
--cc=laser@zhengmai.com.cn \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox