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

["Weiping He" <laser@zhengmai.com.cn>]

> 
> >     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?

no, there is the only log I can find related in syslog, but I'v seen some kernel stack dump on the screen, 
and I havn't got chance to copy them out. I'm observing it now, if I repeat the error, I'll sent them.

> 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.
> 

yeah, that's what I thought too.

> Right now it looks more like a HW problem.

I guest so at present, but let me wait to see if I can repeat the problem later.

> Can you dig more messages from your kernel log.

there are some other log messages in /var/log/debug, looks like:

----------------------------------------------8<-----------------------------------------
Dec 26 01:58:55 x200 kernel: journal_read_transaction, commit offset 5581 had bad time 232573 or length 4
Dec 26 01:58:55 x200 kernel: journal-1299: Setting newest_mount_id to 28
Dec 26 02:07:06 x200 kernel: CPU: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor = 0
Dec 26 02:07:06 x200 kernel: CPU: After vendor init, caps: 0383f9ff 00000000 00000000 00000000
Dec 26 02:07:06 x200 kernel: CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000000
Dec 26 02:07:06 x200 kernel: CPU:             Common caps: 0383f9ff 00000000 00000000 00000000
Dec 26 02:07:10 x200 kernel: journal-1153: found in header: first_unflushed_offset 405, last_flushed_trans_id 119668
Dec 26 02:07:10 x200 kernel: journal-1206: Starting replay from offset 405, trans_id 119669
Dec 26 02:07:11 x200 kernel: journal-1299: Setting newest_mount_id to 34
Dec 26 02:07:12 x200 kernel: journal-1153: found in header: first_unflushed_offset 7579, last_flushed_trans_id 15604
Dec 26 02:07:12 x200 kernel: journal-1206: Starting replay from offset 7579, trans_id 15605
Dec 26 02:07:12 x200 kernel: journal-1299: Setting newest_mount_id to 34
Dec 26 02:07:12 x200 kernel: journal-1153: found in header: first_unflushed_offset 4260, last_flushed_trans_id 44372
----------------------------------------------8<-----------------------------------------

but I think their are unrelevented here, because I think their are the normal log check after power failure.

> Can you try to run reiserfsck on a problematic partition and see
> if there is anything wrong?

I've run it using command like :

#reiserfsck -x -o -l logfile /dev/sdc6

to all my partitions in linux, and  the `logfile' is empty, so may be I should observing to 
see if the problem could repeated and get more information.
BTW: if there another log helpful I can found, please inform me, I just checked `syslog',
`message' and `debug' in my system log directory.

    Thanks and Regards   Laser
ý:.žË›±Êâmçë¢kaŠÉb²ßìzwm…ébïîžË›±Êâmébžìÿ‘êçz_âžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣømšSåy«\x1e­æ¶\x17…\x01\x06­†ÛiÿÿðÃ\x0fí»\x1fè®\x0få’i\x7f