From: "Sonke Ruempler" <ruempler@topconcepts.com>
To: "Oleg Drokin" <green@namesys.com>
Cc: <linux-kernel@vger.kernel.org>, <reiserfs-list@namesys.com>
Subject: Re: reiserfs bug
Date: Thu, 28 Nov 2002 09:50:55 +0100 [thread overview]
Message-ID: <077201c296bb$43b4ac40$6600a8c0@topconcepts.net> (raw)
In-Reply-To: 20021128114755.A2724@namesys.com
> There should be another message in your logs prior to above,
> can you please tell us what was that message?
Nov 28 09:00:12 blah kernel: reiserfs: checking transaction log (device
08:01) ...
Nov 28 09:00:15 blah kernel: reiserfs: replayed 19 transactions in 3 seconds
Nov 28 09:00:15 blah kernel: Using r5 hash to sort names
Nov 28 09:00:15 blah kernel: ReiserFS version 3.6.25
Nov 28 09:00:51 blah kernel: smb_proc_readdir_long:
name=\topconcepts.net\www\pub\doc\_php_manual_ger\www.php.net\SEARC~-N.PHP\*
, result=-2, rcls=1, err=2
Nov 28 09:00:51 blah kernel: smb_proc_readdir_long:
name=\topconcepts.net\www\pub\doc\_php_manual_ger\www.php.net\SOURC~W#.PHP\*
, result=-2, rcls=1, err=2
Nov 28 09:05:15 blah kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
return code = 10000
Nov 28 09:05:15 blah kernel: I/O error: dev 08:11, sector 283064
Nov 28 09:05:15 blah kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
return code = 10000
Nov 28 09:05:15 blah kernel: I/O error: dev 08:11, sector 283064
Nov 28 09:05:15 blah kernel: zam-7001: io error in reiserfs_find_entry
Nov 28 09:05:15 blah kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
return code = 10000
Nov 28 09:05:15 blah kernel: I/O error: dev 08:11, sector 283064
Nov 28 09:05:15 blah kernel: vs-13050: reiserfs_update_sd: i/o failure
occurred trying to update [2 58464 0x0 SD] stat dataSCSI disk error : host 2
channel 0 id 1 lun 0 return code = 10000
Nov 28 09:05:15 blah kernel: I/O error: dev 08:11, sector 283064
Nov 28 09:05:20 blah kernel: vs-13050: reiserfs_update_sd: i/o failure
occurred trying to update [2 58464 0x0 SD] stat dataSCSI disk error : host 2
channel 0 id 1 lun 0 return code = 10000
Nov 28 09:05:20 blah kernel: I/O error: dev 08:11, sector 11496
Nov 28 09:05:20 blah kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
return code = 10000
Nov 28 09:05:20 blah kernel: I/O error: dev 08:11, sector 11504
Nov 28 09:05:20 blah kernel: journal-601, buffer write failed
Nov 28 09:05:20 blah kernel: kernel BUG at prints.c:334!
Nov 28 09:05:20 blah kernel: invalid operand: 0000
Nov 28 09:05:20 blah kernel: CPU: 0
[...]
If you need more logs, just mail me.
next prev parent reply other threads:[~2002-11-28 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 8:28 reiserfs bug Sönke Ruempler
2002-11-28 8:47 ` Oleg Drokin
2002-11-28 8:50 ` Sonke Ruempler [this message]
2002-11-28 8:57 ` Oleg Drokin
2002-11-28 9:04 ` Sonke Ruempler
2002-11-28 9:09 ` Oleg Drokin
2002-11-28 9:12 ` Sonke Ruempler
2002-11-28 9:13 ` Henning P. Schmiedehausen
2002-11-28 10:03 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2005-01-22 23:26 Pablo Barbáchano
2005-01-23 11:13 ` Pablo Barbáchano
2004-07-01 6:09 Hongwei Li
2004-07-01 20:44 ` Oleg Drokin
2004-10-05 15:01 ` Vladimir Saveliev
2001-10-08 16:44 ReiserFS Bug Aleksander Adamowski
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='077201c296bb$43b4ac40$6600a8c0@topconcepts.net' \
--to=ruempler@topconcepts.com \
--cc=green@namesys.com \
--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