From: "J.A. Magallon" <jamagallon@able.es>
To: Joerg Sommrey <jo@sommrey.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11-rc5: Promise SATA150 TX4 failure
Date: Tue, 01 Mar 2005 23:37:27 +0000 [thread overview]
Message-ID: <1109720247l.10975l.0l@werewolf.able.es> (raw)
In-Reply-To: <20050301014514.GA10653@sommrey.de>
On 03.01, Joerg Sommrey wrote:
> Hi all,
>
> a problem that was introduced between 2.6.10-ac9 and 2.6.10-ac11 made
> it's way into 2.6.11-rc5. While taking a backup onto a SCSI-streamer one
> of my RAID1-arrays gets corrupted. Afterwards the system hangs and
> isn't even bootable. Need to raidhotadd the failed partition in single
> user mode to get the box working again. Error messages:
>
Me too :(. Just a slightly different case.
I have a server with 6x250Gb SATA drives, hanged on a pair of Promise
PDC20319 (FastTrak S150 TX4) (rev 02) controlers (each has 4 ports).
Main use for the box is as a smb/atalk/nfs server.
With 2.6.20-rc3-mm2+libata-dev2, the box is stable, we can drop
gigs of files throug samba amd it works.
Anything newer that that makes the box hang siliently, no messages,
no oops. It also happened to me with just a local wget of a big
file (oofice-2.0-beta), after download the box locked hard.
I tried to apply libata-dev1 on top of newer kernels, but part of it
is already there, and the rest drops too many rejects/offsets for
me.
I also have one other problem with flock, but thats subject for another
post...
Any ideas about what changed wrt sata ?
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam12 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #1
prev parent reply other threads:[~2005-03-01 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 1:45 Joerg Sommrey
2005-03-01 23:37 ` J.A. Magallon [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=1109720247l.10975l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jo@sommrey.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome