From: Maciej Matysiak <phoner.reiserfs@blah.pl>
To: reiserfs-list@namesys.com
Subject: Re: kernel BUG at prints.c:334
Date: Mon, 06 Jan 2003 10:23:52 +0100 [thread overview]
Message-ID: <hh4r8mtyvr.fsf@blah.pl> (raw)
In-Reply-To: <20030106104436.A2174@namesys.com> (Oleg Drokin's message of "Mon, 6 Jan 2003 10:44:36 +0300")
On the 6th of January 2003 at 08:44, Oleg Drokin <green#namesys.com> wrote:
>> btw., it appears for me that ibm disks have something like 'y2k3 problem'.
>> it's a poor joke, but i got already 3 ibm disks that died in my servers
>> this year. that one was working not even 3 weeks. all of them scsi, made in
>> hungary
> Ones from Hungary had pretty much of bad press for two years already starting
> with infamous (IDE) DTLA-307030 series, I believe.
all my dead ibm disks are scsi. that last was identified as IC35L036UWD210-0.
>>> Yes, reiserfs is not very well prepared to I/O errors while writing to
>>> journal, hence it panicked.
>> but could the errors be a bit more descriptive, please :)
> It said "I/O error doing so and so".
> And lots of SCSI diagnostic from SCSI layer prior to that.
> What do you consider to be more informative message (with example, please).
after thinking a bit more about that and looking at the logs again, i have to
admit that you're absolutely right. sorry for the noise.
m.m.
--
use gnus, not guns!
next prev parent reply other threads:[~2003-01-06 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 16:14 kernel BUG at prints.c:334 Maciej Matysiak
2003-01-06 7:11 ` Oleg Drokin
2003-01-06 7:36 ` Maciej Matysiak
2003-01-06 7:44 ` Oleg Drokin
2003-01-06 9:23 ` Maciej Matysiak [this message]
2003-01-06 8:42 ` Hans Reiser
2003-01-06 17:02 ` Valdis.Kletnieks
2003-01-10 17:07 ` Any paper on Journaling algorithm? bmoon
2003-01-13 15:53 ` Hans Reiser
[not found] ` <3E22ECF0.9050605@emageon.com>
2003-01-13 18:57 ` Hans Reiser
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=hh4r8mtyvr.fsf@blah.pl \
--to=phoner.reiserfs@blah.pl \
--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 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.