<?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 Re: Performing a linux rescan of newly added LUNS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088845#M63364</link>
    <description>Hello Paul, &lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi-qlascan" &amp;gt; /proc/scsi/&lt;DRIVER-NAME&gt;/&lt;ADAPTER-ID&gt; &lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi add-single-device 0 1 2 3" &amp;gt;/proc/scsi/scsi &lt;BR /&gt;&lt;BR /&gt;Try not to issue above command while SAN Backup (NetBackup, Data Protector) is running. There are possibilities that the SAN Backup could be interrupted.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/ADAPTER-ID&gt;&lt;/DRIVER-NAME&gt;</description>
    <pubDate>Thu, 25 Oct 2007 21:10:06 GMT</pubDate>
    <dc:creator>TY 007</dc:creator>
    <dc:date>2007-10-25T21:10:06Z</dc:date>
    <item>
      <title>Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088839#M63358</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;I have read a number of posts on the qlogic website and internet in general about getting newly added luns recognised without a reboot. I have tried running the hp_fibreutils hp_rescan / xpinfo / and found a decent post advising the following &lt;BR /&gt;&lt;BR /&gt;Question&lt;BR /&gt;&lt;BR /&gt;Can devices be rescanned in Linux OS without reloading the Linux driver?&lt;BR /&gt;&lt;BR /&gt;A new LUN was added to the storage, but the LUN cannot be seen by the driver or the OS.  Rebooting or reloading the driver would be too disruptive.&lt;BR /&gt;Answer&lt;BR /&gt;&lt;BR /&gt;There is a procedure which forces the driver to rescan the targets to allow a new device to be added.  This triggers the driver to initiate a LUN discovery process.&lt;BR /&gt;&lt;BR /&gt;To force a rescan from the command line, type the following command:&lt;BR /&gt;# echo "scsi-qlascan" &amp;gt; /proc/scsi/&lt;DRIVER-NAME&gt;/&lt;ADAPTER-ID&gt;&lt;BR /&gt;&lt;BR /&gt;Where:&lt;BR /&gt;- &lt;DRIVER-NAME&gt;  = qla2100, qla2200, qla2300 (2.4 kernel drivers) or qla2xxx (2.6 kernel drivers)&lt;BR /&gt;- &lt;ADAPTER-ID&gt; = the instance number of the HBA&lt;BR /&gt;&lt;BR /&gt;After executing this command, force the SCSI mid layer to do its own scan and build the device table entry for the new device by typing the following command:&lt;BR /&gt;# echo "scsi add-single-device 0 1 2 3" &amp;gt;/proc/scsi/scsi&lt;BR /&gt;&lt;BR /&gt;Where:&lt;BR /&gt;-  "0 1 2 3" = your "Host Channel ID LUN"&lt;BR /&gt;&lt;BR /&gt;The scanning must be done in the above mentioned order: first the driver (qla2300/qla2200 driver, etc.), and then the Linux SCSI mid layer (i.e. OS scan).&lt;BR /&gt;Operating System&lt;BR /&gt;Linux Red Hat&lt;BR /&gt;Linux SUSE&lt;BR /&gt;&lt;BR /&gt;I can try this but dont know how to find the HOST / Channel / ID / LUN&lt;BR /&gt;of the new luns.&lt;BR /&gt;&lt;BR /&gt;The storage guys have added 4 new luns and /proc/scsi/scsi shows 77 disks, but /proc/scsi/qla2xxx/0 shows 73 so it seems the scsi layer sees them, but not the qlogic card correctly.&lt;BR /&gt;&lt;BR /&gt;Im using the 2.6.9-11 kernel on redhat.&lt;/ADAPTER-ID&gt;&lt;/DRIVER-NAME&gt;&lt;/ADAPTER-ID&gt;&lt;/DRIVER-NAME&gt;</description>
      <pubDate>Fri, 19 Oct 2007 08:27:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088839#M63358</guid>
      <dc:creator>Paul Thomson_2</dc:creator>
      <dc:date>2007-10-19T08:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088840#M63359</link>
      <description>There is a script that handles /proc/scsi/scsi, and it's called rescan-scsi-bus.sh.&lt;BR /&gt;&lt;BR /&gt;Normally, hp_rescan should do the job.</description>
      <pubDate>Fri, 19 Oct 2007 08:51:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088840#M63359</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-10-19T08:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088841#M63360</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You may well be able to pick up the relevant information in the output of "dmesg"&lt;BR /&gt;&lt;BR /&gt;Failing that, the commands "lssd" and "lssg" may be of use...&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Rob</description>
      <pubDate>Sun, 21 Oct 2007 06:37:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088841#M63360</guid>
      <dc:creator>Rob Leadbeater</dc:creator>
      <dc:date>2007-10-21T06:37:37Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088842#M63361</link>
      <description>Hi Paul&lt;BR /&gt;&lt;BR /&gt;you can trigger a scsi-bus rescan by sending string "- - - " to the file named "scan" placed in /sys/class/scsi_host/hostX/&lt;BR /&gt;&lt;BR /&gt;$ cd /sys/class/scsi_host/hostX/&lt;BR /&gt;# where hostX is your qla&lt;BR /&gt;# maybe file hostX/proc_name is helpful to  # identify the correct one.&lt;BR /&gt;&lt;BR /&gt;then:&lt;BR /&gt;$ echo "- - - " &amp;gt; scan&lt;BR /&gt;and&lt;BR /&gt;$ dmesg | tail&lt;BR /&gt;or&lt;BR /&gt;cat /proc/scsi/scsi&lt;BR /&gt;&lt;BR /&gt;hope this helps.&lt;BR /&gt;rgds&lt;BR /&gt;HGH&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Oct 2007 05:51:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088842#M63361</guid>
      <dc:creator>Hemmetter</dc:creator>
      <dc:date>2007-10-22T05:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088843#M63362</link>
      <description>you may download the qlun_disc.sh from qlogic's web site.&lt;BR /&gt;&lt;BR /&gt;This script is a command utility, which will help to Perfom the followings&lt;BR /&gt;&lt;BR /&gt;QLogic Linux LUN Scan Utility v2.3&lt;BR /&gt;&lt;BR /&gt;To begin scanning the LUNs issue following command:&lt;BR /&gt;&lt;BR /&gt;  # /opt/local/unix/bin/qlun_disc.sh&lt;BR /&gt;&lt;BR /&gt;Usage: /opt/local/unix/bin/qlun_disc.sh [OPTIONS]&lt;BR /&gt;&lt;BR /&gt;  -cl, --current-luns&lt;BR /&gt;                        Displays LUNS currently present&lt;BR /&gt;&lt;BR /&gt;  -h,  --help, ?&lt;BR /&gt;                        Prints this help message&lt;BR /&gt;&lt;BR /&gt;  -i,  --interactive&lt;BR /&gt;                        Use this option to use the menu driven program&lt;BR /&gt;&lt;BR /&gt;  -p, --proc&lt;BR /&gt;                        Use PROC file system for LUN scanning&lt;BR /&gt;&lt;BR /&gt;  -r, --refresh&lt;BR /&gt;                        To refresh, that is remove LUNs that are lost&lt;BR /&gt;                        use the options "-r|--refresh". This will&lt;BR /&gt;                        remove the LUNs which no more exist.&lt;BR /&gt;&lt;BR /&gt;  -s,  --scan [-r|--refresh]&lt;BR /&gt;                        The QLogic LUN scan utility re-scans all the&lt;BR /&gt;                        devices connected to the QLogic HBA&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Oct 2007 14:12:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088843#M63362</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-10-23T14:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088844#M63363</link>
      <description>Hello Paul,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi-qlascan" &amp;gt; /proc/scsi/&lt;DRIVER-NAME&gt;/&lt;ADAPTER-ID&gt;&lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi add-single-device 0 1 2 3" &amp;gt;/proc/scsi/scsi&lt;BR /&gt;&lt;BR /&gt;Theoritically above commands are safe. If involves Production Server, do consider carefully, worst scenario - Kernel Panic :)&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/ADAPTER-ID&gt;&lt;/DRIVER-NAME&gt;</description>
      <pubDate>Thu, 25 Oct 2007 06:00:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088844#M63363</guid>
      <dc:creator>TY 007</dc:creator>
      <dc:date>2007-10-25T06:00:15Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088845#M63364</link>
      <description>Hello Paul, &lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi-qlascan" &amp;gt; /proc/scsi/&lt;DRIVER-NAME&gt;/&lt;ADAPTER-ID&gt; &lt;BR /&gt;&amp;gt;&amp;gt; echo "scsi add-single-device 0 1 2 3" &amp;gt;/proc/scsi/scsi &lt;BR /&gt;&lt;BR /&gt;Try not to issue above command while SAN Backup (NetBackup, Data Protector) is running. There are possibilities that the SAN Backup could be interrupted.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/ADAPTER-ID&gt;&lt;/DRIVER-NAME&gt;</description>
      <pubDate>Thu, 25 Oct 2007 21:10:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088845#M63364</guid>
      <dc:creator>TY 007</dc:creator>
      <dc:date>2007-10-25T21:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088846#M63365</link>
      <description>Hi I have tried these and with variations they do work so thanks to everyone.  By this I can dynamically add the LUNS without reboot and then format them. &lt;BR /&gt;&lt;BR /&gt;However, via SANsurfer we are using the following settings in /etc/modprobe.conf &lt;BR /&gt;options qla2xxx ConfigRequired=1  ql2xmaxqdepth=16 qlport_down_retry=30 ql2xlogi&lt;BR /&gt;nretrycount=16 ql2xfailover=1 ql2xlbType=1 ql2xautorestore=0x80&lt;BR /&gt;&lt;BR /&gt;In order to get the Qlogic cards to register the new LUNS in SANsurfer I need to reboot.  I am currently asking HP about this because if the LUNS are not visible in SANsurfer, if my primary fibre card failed and all luns used the failover card would the new LUNS be usable ?&lt;BR /&gt;&lt;BR /&gt;Any thoughts ?&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Oct 2007 02:25:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088846#M63365</guid>
      <dc:creator>Paul Thomson_2</dc:creator>
      <dc:date>2007-10-26T02:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088847#M63366</link>
      <description>&lt;BR /&gt;SAN surfer is a swicth manager s/w(if is understand right) and does not replace the path fail over s/w like power path module&lt;BR /&gt;&lt;BR /&gt;What software do you use for path fail over facility?So what SANsurfer could not see is some thing different(asuume not related)to how the path management s/w responds to a fiber card failure.</description>
      <pubDate>Tue, 30 Oct 2007 14:49:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088847#M63366</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-10-30T14:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: Performing a linux rescan of newly added LUNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088848#M63367</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I noticed that when removing a scsi LUN from the array without rebooting, after rescan, it is still showing up in /proc/scsi/scsi, it this the correct Linux behavior or something to do with qla2xxx driver or a bug, is the driver supposing to inform scsi mid layer about this removal and scsi mid layer will update its own LUN list or not? &lt;BR /&gt;&lt;BR /&gt;Thanks for the information.</description>
      <pubDate>Sat, 29 Dec 2007 01:34:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/performing-a-linux-rescan-of-newly-added-luns/m-p/4088848#M63367</guid>
      <dc:creator>mike_Stephen</dc:creator>
      <dc:date>2007-12-29T01:34:51Z</dc:date>
    </item>
  </channel>
</rss>

