From: Bernd Schubert <bernd-schubert@web.de>
To: Fabien Salvi <fabien@cri74.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: i/o errors
Date: Wed, 23 Jun 2004 17:08:37 +0200 [thread overview]
Message-ID: <200406231708.40264.bernd-schubert@web.de> (raw)
In-Reply-To: <40D98D10.4090205@cri74.org>
> I won't be surprised if it's a hardware related problem.
> Do you know which is the real manufacturer of the RAID controller and
> firmware ? I don't think Transtec make their own system...
As far as I know its an Infortrend device, at least the manual and usage
information are similar with an infortrend device. If you have interest, I
could try to find out which of the infortrend devices it is.
>
> IMHO, you should try big bench without DRDB using I/O benchmark tool and
> also simply dd to make big parallel transfers and check if you can
> reproduce the bug. It would be interested, if you get the bug, to try
> with other linux kernel revision and also other OS...
Of course, I already performed those benchmarks, however only on the
filesystem and I never could reproduce those bugs. Tomorrow afternoon I will
try what happens without the filesystem.
Maybe the filesystem layer speed degrading is sufficient to prevent the bug.
When the problem first occured and asked Justin about it, he told me to use
his newer driver versions. Then I really thought that it is a driver bug,
because it got worse with every driver revision. Finally Justin told me that
every revision became slightly faster - this slight speed increase was enough
to reliably trigger this bug :/
We are trying to fix this bug for more than four weeks now, and finally we
would like to use our new storage server. However, I'm really worried that
this problem will occur during the real usage, though my tests showed that it
shouldn't happen in real live.
I really would prever not to use an other OS, since I have no recent
experience with them.
>
> Good luck!
Thanks at lot!
Cheers,
Bernd
--
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-06-23 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 9:42 i/o errors Bernd Schubert
2004-06-23 14:00 ` Fabien Salvi
2004-06-23 15:08 ` Bernd Schubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 0:38 I/O Errors f00bar
2004-09-27 15:53 ` Alex Zarochentsev
2004-09-28 0:26 ` f00bar
2004-09-28 15:02 ` E.Gryaznova
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=200406231708.40264.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=fabien@cri74.org \
--cc=linux-scsi@vger.kernel.org \
/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.