<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic HBA failover in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054104#M48729</link>
    <description>I am trying to test the failover of the HBA )Hp-1242SR)running on RHEL4 to an EVA 5000. I am using the hp linux driver kit. It has one active path to the EVA. I had a file transfer running and disconnected the active port and it failed over fine to port2. But when port1 was plugged back in the transfer cotinued on port2.&lt;BR /&gt;Sansurfer shows all other luns failed over to the alternate path and then failed back to the preffered path when the link came back except for the lun to which the data was being written to. That still shows as using alternate and is not failing back. Is there anything that needs to be done to force this? Reboot? Or is there any there command to do this?</description>
    <pubDate>Wed, 20 Jun 2007 17:03:46 GMT</pubDate>
    <dc:creator>unre4l</dc:creator>
    <dc:date>2007-06-20T17:03:46Z</dc:date>
    <item>
      <title>HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054104#M48729</link>
      <description>I am trying to test the failover of the HBA )Hp-1242SR)running on RHEL4 to an EVA 5000. I am using the hp linux driver kit. It has one active path to the EVA. I had a file transfer running and disconnected the active port and it failed over fine to port2. But when port1 was plugged back in the transfer cotinued on port2.&lt;BR /&gt;Sansurfer shows all other luns failed over to the alternate path and then failed back to the preffered path when the link came back except for the lun to which the data was being written to. That still shows as using alternate and is not failing back. Is there anything that needs to be done to force this? Reboot? Or is there any there command to do this?</description>
      <pubDate>Wed, 20 Jun 2007 17:03:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054104#M48729</guid>
      <dc:creator>unre4l</dc:creator>
      <dc:date>2007-06-20T17:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054105#M48730</link>
      <description>I also see this in the var log messages just for the lun that was failoved over but did not fail back. The other luns show up fine.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;qla2x00: no more failovers for request - pid= 564&lt;BR /&gt;SCSI device sdd: 849346560 512-byte hdwr sectors (434865 MB)&lt;BR /&gt;qla2x00: no more failovers for request - pid= 568 &lt;BR /&gt;sdd: asking for cache data failed            &lt;BR /&gt;sdd: assuming drive cache: write through&lt;BR /&gt;qla2x00: no more failovers for request - pid= 569&lt;BR /&gt;SCSI device sdd: 849346560 512-byte hdwr sectors (434865 MB)&lt;BR /&gt;qla2x00_combine_by_lunid: Found a controller path 0x0 - lun 0&lt;BR /&gt;qla2x00: no more failovers for request - pid= 573 &lt;BR /&gt;sdd: asking for cache data failed&lt;BR /&gt;sdd: assuming drive cache: write through&lt;BR /&gt;sdd:&amp;lt;6&amp;gt;qla2x00: no more failovers for request - pid= 574&lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;end_request: I/O error, dev sdd, sector 0&lt;BR /&gt;Buffer I/O error on device sdd, logical block 0&lt;BR /&gt;qla2x00: no more failovers for request - pid= 575&lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;end_request: I/O error, dev sdd, sector 0&lt;BR /&gt;Buffer I/O error on device sdd, logical block 0&lt;BR /&gt;qla2x00: no more failovers for request - pid= 576&lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;end_request: I/O error, dev sdd, sector 0&lt;BR /&gt;Buffer I/O error on device sdd, logical block 0&lt;BR /&gt;unable to read partition table&lt;BR /&gt;&lt;BR /&gt;I am using the 2.6.9.55 hugemem kernel and the latest 8.01.06 version of the linux driver kit.</description>
      <pubDate>Wed, 20 Jun 2007 18:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054105#M48730</guid>
      <dc:creator>unre4l</dc:creator>
      <dc:date>2007-06-20T18:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054106#M48731</link>
      <description>dumb question, for the virtual disk, what is the preferred presentation path?</description>
      <pubDate>Thu, 21 Jun 2007 13:53:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054106#M48731</guid>
      <dc:creator>Court Campbell</dc:creator>
      <dc:date>2007-06-21T13:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054107#M48732</link>
      <description>Prefferd path is A. Mode is failover only. The strange thing is it only happens for one of the 4 luns presented. I have tried different driver versions too. It loads sdc fine but when it comes to sdd it errors out and then loads sde and sdf fine. I can do an fdisk on sdd once the system comes up and i repartitioned it and formatted it but still it errors when i restart the system. Here is the log when booting up.&lt;BR /&gt;Any help is appreciated.&lt;BR /&gt;&lt;BR /&gt;Vendor: COMPAQ    Model: HSV110 (C)COMPAQ  Rev: 3028&lt;BR /&gt;Type:   RAID                               ANSI SCSI revision: 02&lt;BR /&gt;qla2400 0000:0a:00.0: scsi(3:0:0:0): Enabled tagged queuing, queue depth 16.&lt;BR /&gt;Vendor: COMPAQ    Model: HSV110 (C)COMPAQ  Rev: 3028&lt;BR /&gt;Type:   Direct-Access                      ANSI SCSI revision: 02&lt;BR /&gt;qla2400 0000:0a:00.0: scsi(3:0:0:1): Enabled tagged queuing, queue depth 16.&lt;BR /&gt;SCSI device sdc: 83886080 512-byte hdwr sectors (42950 MB) &lt;BR /&gt;SCSI device sdc: drive cache: write through&lt;BR /&gt;SCSI device sdc: 83886080 512-byte hdwr sectors (42950 MB) &lt;BR /&gt;SCSI device sdc: drive cache: write through sdc: sdc1 &lt;BR /&gt;Attached scsi disk sdc at scsi3, channel 0, id 0, lun 1&lt;BR /&gt;&lt;BR /&gt;Vendor: COMPAQ    Model: HSV110 (C)COMPAQ  Rev: 3028&lt;BR /&gt;Type:   Direct-Access                      ANSI SCSI revision: 02&lt;BR /&gt;qla2400 0000:0a:00.0: scsi(3:0:0:2): Enabled tagged queuing, queue depth 16.&lt;BR /&gt;qla2x00: no more failovers for request - pid= 564 &lt;BR /&gt;SCSI device sdd: 849346560 512-byte hdwr sectors (434865 MB) &lt;BR /&gt;qla2x00: no more failovers for request - pid= 568&lt;BR /&gt;sdd: asking for cache data failed&lt;BR /&gt;sdd: assuming drive cache: write through     &lt;BR /&gt;qla2x00: no more failovers for request - pid= 569 &lt;BR /&gt;SCSI device sdd: 849346560 512-byte hdwr sectors (434865 MB) &lt;BR /&gt;qla2x00_combine_by_lunid: Found a controller path 0x0 - lun 0&lt;BR /&gt;qla2x00: no more failovers for request - pid= 573 &lt;BR /&gt;asking for cache data failed&lt;BR /&gt;sdd: assuming drive cache: write through sdd:&amp;lt;6&amp;gt;qla2x00: no more failovers for request - pid= 574&lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;rc: Starting lm_sensors:  succeeded Jun 21 18:43:13 bsdb kernel: end_request: I/O error, dev sdd, sector 0 &lt;BR /&gt;Buffer I/O error on device sdd, logical block 0&lt;BR /&gt;qla2x00: no more failovers for request - pid= 575 &lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;end_request: I/O error, dev sdd, sector 0&lt;BR /&gt;Buffer I/O error on device sdd, logical block 0 &lt;BR /&gt;qla2x00: no more failovers for request - pid= 576&lt;BR /&gt;Device sdd not ready.&lt;BR /&gt;end_request: I/O error, dev sdd, sector 0 &lt;BR /&gt;Buffer I/O error on device sdd, logical block 0&lt;BR /&gt;unable to read partition table&lt;BR /&gt;Attached scsi disk sdd at scsi3, channel 0, id 0, lun 2</description>
      <pubDate>Thu, 21 Jun 2007 19:12:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054107#M48732</guid>
      <dc:creator>unre4l</dc:creator>
      <dc:date>2007-06-21T19:12:52Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054108#M48733</link>
      <description>The fail over to port2 is auotmatic .Fail back to port1 had not happened as the disk is in use and it may not be automatic&lt;BR /&gt;&lt;BR /&gt;Could you unplug port2 and check if it is fail over to port1.If this functions well, you are safe interms of data integrity.</description>
      <pubDate>Sun, 24 Jun 2007 09:08:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054108#M48733</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-06-24T09:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054109#M48734</link>
      <description>Yes when i unplug port 2 it does fail over to port 1 and that works well. It's just that when it is failed over to port 2 and i reboot the luns on port 2 do not show up during boot up ad the system scans for luns only on port1.</description>
      <pubDate>Tue, 26 Jun 2007 10:43:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054109#M48734</guid>
      <dc:creator>Kumar Raman</dc:creator>
      <dc:date>2007-06-26T10:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054110#M48735</link>
      <description>what is vgdisplay shows at that time? which path shows as primary and alternate? If it fails over then vgdisplay should show port1 as alternate path.&lt;BR /&gt;&lt;BR /&gt;  No need to reboot server. since your file transfer continuing on port2, it won't fail back to port1 even if connect port1 back. But if you want to test it then during file transfer, unplug port2 and see if it fails back to port1.</description>
      <pubDate>Wed, 27 Jun 2007 13:43:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054110#M48735</guid>
      <dc:creator>IT_2007</dc:creator>
      <dc:date>2007-06-27T13:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: HBA failover</title>
      <link>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054111#M48736</link>
      <description>Was a port error on the switch, changing to different ports on the switches fixed the errors.</description>
      <pubDate>Sat, 30 Jun 2007 13:32:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/hba-failover/m-p/5054111#M48736</guid>
      <dc:creator>unre4l</dc:creator>
      <dc:date>2007-06-30T13:32:58Z</dc:date>
    </item>
  </channel>
</rss>

