[7078] in linux-scsi channel archive
Re: SCSI /dev/sg question
daemon@ATHENA.MIT.EDU (Russ Savela)
Mon Aug 30 12:31:37 1999
Date: Mon, 30 Aug 1999 12:30:01 -0400 (EDT)
From: Russ Savela <savela@WPI.EDU>
To: Kurt Garloff <garloff@suse.de>
cc: gokhan sozmen <gokhan_sozmen@hotbot.com>,
linux-scsi@vger.rutgers.edu, linux-kernel@vger.rutgers.edu
In-Reply-To: <19990830162156.B9578@kurt.kdt.de>
This is a chicken/egg type problem. A lot of raid controllers can't be
managed until a lun is created (since there aren't any devices).
Some work around this by having a pass through driver that is installed to
configure the array. Once this is done, the driver is removed.
A lot of lower-end controller boards just use dos utilities, but many
higher end / external controllers just don't work that way.
-russ
>
> You need special tools to set up your SCSI config. I don't think, your
> Hardware RAID will be configurable by SCSI commands sent to it.
>
> If you have a hardware RAID, it should provide you the possibility to have
> config data exchanged in some way. Maybe by providing a device which you can
> IOCTL or talk to (and I would use a char device rather then simulate a SCSI
> device), but preferably by a /proc/scsi/myraid/? interface.
>
> I didn't look how the RAIDs in Linux do it, BTW. Have a look at the DAC960,
> eata, gdth, megaraid, pci2xx drivers.
>
> Regards,
> --
> Kurt Garloff <garloff@suse.de> Wuppertal, FRG
> PGP2 key: See mail header, key servers Linux kernel development
> SuSE GmbH, Nürnberg, FRG SCSI drivers: tmscsim(DC390), DC395
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
