Re: anybody know about "journal-615" and/or "journal-601" log error?

[Oleg Drokin <green@namesys.com>]

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