archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <>
Subject: Bug during media scan, kernel 2.4.23-pre9
Date: Mon, 3 Nov 2003 18:46:41 +0100	[thread overview]
Message-ID: <> (raw)


I just encountered a real bad problem with using media scan on 3ware
controllers. I have 3 hds connected and configured a RAID5. I use media scan
regularly (daily basis). Since two days I see this problem:

Nov  3 18:12:11 box 3w-xxxx[2039]: INFORMATION: Verify started on unit 0 on
controller ID:2. (0x29)
Nov  3 18:19:41 box kernel: 3w-xxxx: scsi2: Unit #0: Command (f6e5d800) timed
out, resetting card.

After that the box has problems, the controller obviously hangs.
This in itself can be considered a bug, but what is really annoying is that one
has no chance finding out _which_ port caused the problem.
So at this point you can play roulette and replace one of the hds hoping that
it was indeed the bad one.

It would be really a lot better to degrade the unit in this case and give a
hint which port has problems (command timed out on port ...).
This would:
a) not hang the box
b) give you a chance to replace the hd, as you would expect in RAID5

The current situation is absolutely _no good_.


                 reply	other threads:[~2003-11-03 17:46 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).