From: Farkas Levente <lfarkas@bnap.hu>
To: Andreas Kahnt <aka@aka.coware.de>
Cc: linux-raid@vger.kernel.org, ataraid-list@redhat.com,
Adam Radford <aradford@3WARE.com>
Subject: Re: 3ware 7500-8 controller, hardware or software raid, kernel crash
Date: Mon, 05 May 2003 13:22:48 +0200 [thread overview]
Message-ID: <3EB64988.8000809@bnap.hu> (raw)
In-Reply-To: <Pine.LNX.4.44.0305042218040.19228-100000@aka.coware.de>
Andreas Kahnt wrote:
> Hi,
>
>
>>after we format it, start to copy back the data (about 250GB) from nfs.
>>after about 2 minutes the kernel crash with some kind of io error on the
>>3ware controller. unfortunately we don't have time to write down the
>>kernel's error message since this is one of our production enviroment
>>server. what's more I wouldn't like to buy more such card to play with if
>>it's not well functional. you can read the kernel log after that crash at
>>the end of this mail.
>
>
> We had the same problem using SuSE-8.0/2.4.18. We 'solved' the problem using
> 6+1 - Raid-5 and removed the 8. disk. Now the last disk is a cold spare ;-).
> This work well for a couple of months uptime.
are you kidding? hmm:-((
this is the truth??? I'm getting said:-(
do the 3ware are aware of this?
we'd like to buy more such cards, but we've a few server in which 7+1 is
required....
or it's better if I use software raid and in that case the above problem
doesn't occure what's more I've got better performance?
--
Levente "Si vis pacem para bellum!"
prev parent reply other threads:[~2003-05-05 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 12:26 3ware 7500-8 controller, hardware or software raid, kernel crash Farkas Levente
2003-05-04 13:47 ` Mikael Abrahamsson
2003-05-04 20:25 ` Andreas Kahnt
2003-05-05 11:22 ` Farkas Levente [this message]
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=3EB64988.8000809@bnap.hu \
--to=lfarkas@bnap.hu \
--cc=aka@aka.coware.de \
--cc=aradford@3WARE.com \
--cc=ataraid-list@redhat.com \
--cc=linux-raid@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.