* SCSI-Multipath driver for 2.4? @ 2001-04-25 11:15 Christoph Biardzki 2001-04-25 16:17 ` Doug Ledford 2001-04-30 22:42 ` Alan Cox 0 siblings, 2 replies; 4+ messages in thread From: Christoph Biardzki @ 2001-04-25 11:15 UTC (permalink / raw) To: linux-kernel Hi, I wondered whether thera are already effrots to por the Multipath-driver for FibreChannel (http://t3.linuxcare.org) to the 2.4 kernel? This patch allows a transparent failover to another path to FC-attached disk in case the primary path fails. Is there any documentation about the changes in the SCSI-driver interfaces from 2.2 -> 2.4 (eg. in sd.c) ? Christoph ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: SCSI-Multipath driver for 2.4? 2001-04-25 11:15 SCSI-Multipath driver for 2.4? Christoph Biardzki @ 2001-04-25 16:17 ` Doug Ledford 2001-04-25 18:09 ` Jason McMullan 2001-04-30 22:42 ` Alan Cox 1 sibling, 1 reply; 4+ messages in thread From: Doug Ledford @ 2001-04-25 16:17 UTC (permalink / raw) To: Christoph Biardzki; +Cc: linux-kernel Christoph Biardzki wrote: > > Hi, > > I wondered whether thera are already effrots to por the Multipath-driver > for FibreChannel (http://t3.linuxcare.org) to the 2.4 kernel? This patch > allows a transparent failover to another path to FC-attached > disk in case the primary path fails. When we reviewed the code, we didn't like it all that much. It served it's purpose on the t3 stuff from Sun, but it wasn't generic enough to suit our tastes. So, Ingo wrote a multipath RAID extension as part of the MD driver and that's in our 7.1 product and will be sent to the mainstream kernel as soon as it's gotten enough testing to be deemed finished (for instance, there are horribly stupid devices out there that support what is called "Active-Passive" multipath, where if you write to the passive path, it makes the active path error out, which makes the device 100% useless for multi-initiator, shared SCSI/FC environments, and makes the device total junk in my opinion, but if we are going to support them in a Multipath setup, then the multipath driver has to be modified so it doesn't attempt to touch passive paths until the active path has already failed, which it doesn't currently attempt to do when writing superblocks or reading partition tables). > Is there any documentation about the changes in the SCSI-driver interfaces > from 2.2 -> 2.4 (eg. in sd.c) ? -- Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: SCSI-Multipath driver for 2.4? 2001-04-25 16:17 ` Doug Ledford @ 2001-04-25 18:09 ` Jason McMullan 0 siblings, 0 replies; 4+ messages in thread From: Jason McMullan @ 2001-04-25 18:09 UTC (permalink / raw) To: linux-kernel Doug Ledford <dledford@redhat.com> wrote: > When we reviewed the code, we didn't like it all that much. It served it's > purpose on the t3 stuff from Sun, but it wasn't generic enough to suit our > tastes. True, but the MD layer in 2.2.x (at least as of last June, when I wrote the T3 SCSI-Alias-Chain failover code) was poorly documented, race-prone, and nasty. :^) My _first_ attempt at multipath was with the MD layer, but the 2.2.x code was just way too hairy for it to work by the deadlines Sun had on us. So I went into the SCSI block handling layer. Only one major race I had to avoid, and got the final implementation written in a week. > (for instance, there > are horribly stupid devices out there that support what is called > "Active-Passive" multipath, where if you write to the passive path, it makes > the active path error out, which makes the device 100% useless for > multi-initiator, shared SCSI/FC environments, and makes the device total junk > in my opinion, but if we are going to support them in a Multipath setup, then > the multipath driver has to be modified so it doesn't attempt to touch passive > paths until the active path has already failed, which it doesn't currently > attempt to do when writing superblocks or reading partition tables). Interestingly enough, that is exactly the type of hardware that the SCSI Alias Chains patch is designed to support - the Sun T3, IBM Shark, etc. Nasty, evil critters, but supported. I do wish you the best of luck with the MD layer version, since that's where it should have gone in the first place.... If the MD layer had been up to snuff. ];^) -- Jason McMullan, Senior Linux Consultant Linuxcare, Inc. 412.432.6457 tel, 412.656.3519 cell jmcmullan@linuxcare.com, http://www.linuxcare.com/ Linuxcare. Putting open source to work. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: SCSI-Multipath driver for 2.4? 2001-04-25 11:15 SCSI-Multipath driver for 2.4? Christoph Biardzki 2001-04-25 16:17 ` Doug Ledford @ 2001-04-30 22:42 ` Alan Cox 1 sibling, 0 replies; 4+ messages in thread From: Alan Cox @ 2001-04-30 22:42 UTC (permalink / raw) To: Christoph Biardzki; +Cc: linux-kernel > I wondered whether thera are already effrots to por the Multipath-driver > for FibreChannel (http://t3.linuxcare.org) to the 2.4 kernel? This patch > allows a transparent failover to another path to FC-attached > disk in case the primary path fails. Please dont put the multipathing in the scsi layer. Its not uncommon to have raid controllers or other smart devices as the primary FC connection and a dumb scsi layer device as slave ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-04-30 22:39 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2001-04-25 11:15 SCSI-Multipath driver for 2.4? Christoph Biardzki 2001-04-25 16:17 ` Doug Ledford 2001-04-25 18:09 ` Jason McMullan 2001-04-30 22:42 ` Alan Cox
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox