linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-scsi@vger.kernel.org
Subject: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline
Date: Thu, 28 Oct 2004 00:53:02 -0700	[thread overview]
Message-ID: <20041028005302.753a2d52.akpm@osdl.org> (raw)



Begin forwarded message:

Date: Thu, 28 Oct 2004 00:50:31 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline


http://bugme.osdl.org/show_bug.cgi?id=3651

           Summary: dell poweredge 4600 aacraid PERC 3/Di Container goes
                    offline
    Kernel Version: 2.6.10-rc1, 2.6.9, 2.6.8, 2.6.7, 2.6.6
            Status: NEW
          Severity: high
             Owner: andmike@us.ibm.com
         Submitter: oliver.polterauer@ewave.at
                CC: oliver.polterauer@ewave.at


Distribution: Debian Sarge
Hardware Environment: Dell Poweredge 4600, 5 Disks each 146GB in a Raid 5 in 
one container, 8 GB RAM, Dual Xenon 2GHz. The Perc 3/Di Controller is on 
Firmware version 2.80 Build 6092
Software Environment: aacraid
Problem Description: 
The Container on the PERC 3/Di Controller goes offline on heavy I/O Load with 
the following error message:

SCSI:0 (0:0): rejecting I/O to offline device
Buffer I/O error due to I/O error on sda8

Steps to reproduce:

I am using bonnie++ to produce I/O load on the only Volume on the Perc 3/Di 
Controller with the following parameters bonnie++ -d /var/lib/postgres/test -s 
16000 -n 150 -r 8000 -u nobody:nogroup

my partition table:

/dev/sda1 --> /boot (80mb)
/dev/sda2 --> swap (16 GB)
/dev/sda3 --> /root (4 GB)
/dev/sda5 --> /home (4 GB)
/dev/sda6 --> /tmp (1 GB)
/dev/sda7 --> /var (8 GB)
/dev/sda8 --> /var/lib/postgres (502 GB)

Filesystem ext3
kernel is a non modular plain vanilla kernel source (no patches)

I have turned on remote syslog to our syslog server, but it did not log any 
more errormessages as stated above. The error messages above are printed only 
on the console


Best regards,

Oliver

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

             reply	other threads:[~2004-10-28  7:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28  7:53 Andrew Morton [this message]
2004-10-28 18:21 ` Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline Phil Brutsche
2004-11-09 20:22   ` Ryan Anderson
2004-11-09 21:32     ` Otto Solares
2004-11-09 23:49       ` Andrew Kinney
2004-11-10 17:43       ` aacraid, seagate and adaptec issues [Was: Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline] Otto Solares
2004-11-10 20:33         ` Phil Brutsche
2004-11-10 21:08           ` Otto Solares
2004-11-23 21:41 ` Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline Ryan Anderson
2004-11-23 22:58   ` Otto Solares
2004-11-24  1:00   ` Andrew Kinney
2004-11-24 18:35     ` Ryan Anderson

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=20041028005302.753a2d52.akpm@osdl.org \
    --to=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).