linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Carpani <andrea.carpani@criticalpath.net>
To: linux-scsi@vger.kernel.org
Subject: hot-swap problems with Adaptec AIC-7902 (aic79xx)
Date: Wed, 24 Aug 2005 13:29:44 +0200	[thread overview]
Message-ID: <1124882984.13829.33.camel@cronos.criticalpath.it> (raw)

Hi everybody,
here are some issues I'm having with my system dealing with
hot-swapping.

The box is a Tyan GX28 (B2881) B2881G28U4H with 4 Hot-swap U320 SCSI
bays. SCSI controller is Adaptec AIC-7902 dual channel Ultra320 SCSI.

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: FUJITSU  Model: MAP3735NC        Rev: 0108
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: FUJITSU  Model: MAP3735NC        Rev: 0108
  Type:   Direct-Access                    ANSI SCSI revision: 03

Linux kernel 2.6.12.3 (no patches).

I have 2 drives single partition set up as a single md0 software
mirrored raid device (xfs filesystem). I set /dev/sdb1 as faulty and
remove it from the array.

I then want to hot-swap the drive with another one.

echo "scsi remove-single-device 0 0 1 0" > /proc/scsi/scsi

removes it and 

cat /proc/scsi/scsi

shows this. If I physically swap the drive (with a different Maxtor one)
and issue

echo "scsi add-single-device 0 0 1 0" > /proc/scsi/scsi

nothing happens (syslog: 
Aug 24 12:53:48 localhost kernel: scsi0: ILLEGAL_PHASE 0x80
Aug 24 12:53:48 localhost kernel: (scsi0:A:1:0): Abort Message Sent)
and the new drive appears in /proc/scsi/scsi only after a second "echo"
command (I assume this is a power-up delay).

At this point I'm not yet adding the drive to the mirror. The problem is
that if I repeat the last steps more than once (remove-single-device,
swap the drives again, add-single-device) I get the following error on
the console and everything freezes

I/O error in filesystem ("md0") meta-data dev md0 block 0x44308c4
("xlog_iodone") error 5 buf count 1024
Filesystem "md0": Log I/O error detected.
Shutting down filesystem: md0
Please umount the filesystem and rectify the problem(s).

Which is quite strange as I'm only scsi-dealing with the sdb device and
the filesystem at this point should only be on sda.

Here are some questions:
Is it possible that the scsi level operations disturb the other drive?
Which is the correct way to hot-swap scsi disks? Am I doing something
wrong?
More often than not (but not as easily reproducible) the removal and
detection of a new drive fails and the box hangs (no console messages):
could it be a driver/board problem?
Are there well tested scsi adapters/drivers that I should use?
Which scsi debug info should I turn on to help understad the problem?


Thanks,
Andrea.

-- 
Andrea Carpani <andrea.carpani@criticalpath.net>


             reply	other threads:[~2005-08-24 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 11:29 Andrea Carpani [this message]
2005-08-24 14:42 ` hot-swap problems with Adaptec AIC-7902 (aic79xx) bernd

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=1124882984.13829.33.camel@cronos.criticalpath.it \
    --to=andrea.carpani@criticalpath.net \
    --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).