archive mirror
 help / color / mirror / Atom feed
To: (Alex)
Subject: Re: HOT SWAP PROBLEM using hp4100 server series
Date: Wed, 25 Sep 2002 19:24:15 +0100 (BST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> from "Alex" at Sep 24, 2002 01:50:50 PM


> I need some help to test HOT SWAP feature for this drives. I read some 
> documentation and i saw that HOT SWAP may work if my driver for 
> scsi-controller support re-scanning the bus.
> [snip]
> Normal SCSI hardware is not hot-swappable either. It may however work. 
> If your SCSI driver supports re-scanning the bus, and removing and 
> appending devices, you may be able to hot-swap devices.
> I try to check if this feature works for me and don`t. If i remove any 
> scsi drive, this device remain in /proc until will be removed manually, 
> or using a script named which i found it on google.
> I try to obtain some additional info and i saw that for my 
> scsi-controller has 2 active drivers: one older named sym53cxx.o and 
> one newer named sym53cxx_2.o!
> I don`t have for the moment access to this computer but i remember that 
> on default installation, redhat assigned the old driver to my 
> scsi-controller.
> I want to know if i change the driver with this new one, i can use the 
> HOT SWAP feature!
> Are necessary additional settings to be made when i load the new driver 
> or on the system configuration?
> Any success story will be appreciated.

Why do you want to hot swap disks on a SCSI bus which isn't designed for hot swapping?

There is no guarantee that you could keep the server running in the event of a disk failiure - a faulty disk *could* take the whole bus down with it, (it shouldn't do, but you can't guarantee it), so if you are trying to do this to improve reliability, you might be better off looking at using hot spare disks instead.


      reply	other threads:[~2002-09-25 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 10:50 HOT SWAP PROBLEM using hp4100 server series Alex
2002-09-25 18:24 ` jbradford [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:

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