From: "JaniD++" <djani22@dynamicweb.hu>
To: linux-ide@vger.kernel.org
Subject: promise driver stability question (bugreport?)
Date: Thu, 9 Feb 2006 12:11:34 +0100 [thread overview]
Message-ID: <005801c62d69$99298950$9d00a8c0@dcccs> (raw)
Hello, Jeff, list,
10 days ago i have upgrade my system from 8TB to 13.2TB (the system info is
the bottom of mail), and now i have seriously problem with my 2 disk node.
(first i try the sil3112 based cards, but this looks like wery unstable,
makes data lost, very worst write speed with multiple cards and i have
replaced these cards with promise controllers.)
Currently i use the ICH5 , promise sata 300 TX4 and promise sata 300 TX2
cards/chips only.
I use 2.6.16-rc2-git5, because only this kernel knows what i need.
The problem is, one of my disk nodes seriously reboots. (about 4-8 hourly)
I try to catch the error message with remote syslogd, but i cannot see any
valuable info.
At this time i can see the reboot only happens, when the concentrator is
writing to nodes.
The reboot is newer happens, when the node is resyncing, doing recovery
for a long time (~6 hours) and have no other work.
The reboot makes no data lost, except the dirty buffer. (looks like reset)
First i try to track down the problem to hardware, but this looks like good.
(after the system upgrade on the prevously stable nodes, the new hardware is
only the HDD, and the promise cards, plus the kernel.)
Today i try to replace the e1000 nic driver in the kernel with the old, and
known to be stable version, but the reboot happened again. :-(
Is there any info or known bug about promise driver? (or 2.6.16-rc kernels)
What do you recommend to do or try?
Thanks,
Janos
The system info:
4x 3.3TB disk nodes, and one concentrator, without disks.
The nodes:
Abit IS7 motherboard (i865), P4 3G, 1G ram, Intel Gigabit Pro NIC.
4x IDE maxtor 300GB in ICH5
2x SATA maxtor 300GB in ICH5-sata
4x SATA maxtor 300GB in Promise sata 300 TX4
2x SATA maxtor 300GB in Promise sata 300 TX2
reply other threads:[~2006-02-09 11:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='005801c62d69$99298950$9d00a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-ide@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.