<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://ssl.webangel.ie/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://ssl.webangel.ie/feed.php">
        <title>Opbzil - linux:linux-san</title>
        <description></description>
        <link>http://ssl.webangel.ie/</link>
        <image rdf:resource="http://ssl.webangel.ie/lib/exe/fetch.php?media=wiki:dokuwiki.svg" />
       <dc:date>2026-05-28T10:33:59+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:add-luns&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:daemons&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath-conf&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:documentation&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:fiber&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:iscsi&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:local-disks&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:lvm&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:mpathconf&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:newer-kernel&amp;rev=1759830220&amp;do=diff"/>
                <rdf:li rdf:resource="http://ssl.webangel.ie/doku.php?id=linux:linux-san:older-kernels&amp;rev=1759830220&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://ssl.webangel.ie/lib/exe/fetch.php?media=wiki:dokuwiki.svg">
        <title>Opbzil</title>
        <link>http://ssl.webangel.ie/</link>
        <url>http://ssl.webangel.ie/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:add-luns&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>add-luns</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:add-luns&amp;rev=1759830220&amp;do=diff</link>
        <description>Adding Luns

I have not tried this procedure I ussually recommend rebooting server

Adding a LUN
To add a new LUN to an existing PowerPath configuration:

	*  Ordered List ItemScan the bus for the LUNs.
	*  Ensure that the new LUN is created on the storage side and recognized by Linux.</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:daemons&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>daemons</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:daemons&amp;rev=1759830220&amp;do=diff</link>
        <description>DM-Multipath Daemons

After you edit the multipath.conf file you can run the following commands to load and start it as well as to show you wht is detected.


modprobe dm-multipath
service multipathd start
multipath -v2


The multipath -v2 command prints out multipathed paths that show which devices are multipathed. If the command does not print anything out, ensure that all SAN connections are set up properly and the system is multipathed.</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath-conf&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dm-multipath-conf</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath-conf&amp;rev=1759830220&amp;do=diff</link>
        <description>dm-multipath.conf

The multipath.conf files blacklists EVERYTHING by default. So ensure the first lines are commented out


blacklist {
        devnode &quot;*&quot;
}


After commenting out the general blacklist you can then specify general types of devices to black list or even individual devices.</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dm-multipath</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:dm-multipath&amp;rev=1759830220&amp;do=diff</link>
        <description>DM-Multipath

Device Mapper Commands
  Command    Descriptions    multipath -h    Prints usage information    multipath -ll    Displays the current multipath topology using all available information (sysfs, the device mapper, path checkers, and so on)</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:documentation&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:documentation&amp;rev=1759830220&amp;do=diff</link>
        <description>Documentation

Official Redhat Documentation


[ Accessing HBA information]


[ Adding or Removing Luns]</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:fiber&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fiber</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:fiber&amp;rev=1759830220&amp;do=diff</link>
        <description>Linux and Fiber

As of RHEL 3.7 most of the drivers for HBAs are included on the kernel so no need to install extra drivers.

Getting information about the HBAs though is a different story.

Pre 2.6.11 kernels RHEl4.1 and older

 Older Kernels

Post 2.6.11 Kernels</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:iscsi&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>iscsi</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:iscsi&amp;rev=1759830220&amp;do=diff</link>
        <description>Linux iSCSI

This was first supported on RHEL 3. The procedure to set it up is the same for RHEL 3 and 4. For newer versions of RHEL the procedure has changed a bit.

iSCSI in RHEL 3 and 4

 iSCSI in RHEL3 and RHEL4

iSCSI in RHEL 5 and Higher

FIXME need to test this

 iSCSI in RHEL5 and Newer

Documentation</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:local-disks&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>local-disks</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:local-disks&amp;rev=1759830220&amp;do=diff</link>
        <description>Configure DM Multipath to Ignore Local Disks

Details from Redhat Manual

	*  Determine which disks are the internal disks and mark them as the ones to blacklist. In this example, /dev/sda is the internal disk. Note that as originally configured in the default multipath configuration file, executing the</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:lvm&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lvm</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:lvm&amp;rev=1759830220&amp;do=diff</link>
        <description>Using LVM

LVM is Linux&#039;s Volume Management. It is a default during installation

Creating a new LVM

This is done in 3 main steps

- Create a new partition on a disk and marking as type 8e then run 
pvcreate /dev/sdX#

- Create a new Volume group set run **vgcreate **</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:mpathconf&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mpathconf</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:mpathconf&amp;rev=1759830220&amp;do=diff</link>
        <description>Mpathconf

You set up multipath with the mpathconf utility, which creates the multipath configuration file /etc/multipath.conf.

	*  If the /etc/multipath.conf file already exists, the mpathconf utility will edit it.
	*  If the /etc/multipath.conf file does not exist, the mpathconf utility will use the</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:newer-kernel&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>newer-kernel</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:newer-kernel&amp;rev=1759830220&amp;do=diff</link>
        <description>Newer Kernels post 2.6.11

Neer kernels have introduced a lot of changes to the HBA drivers. Now the drivers store the information on various entries in the /sys folder. There is no central information repository of information as on previous versions</description>
    </item>
    <item rdf:about="http://ssl.webangel.ie/doku.php?id=linux:linux-san:older-kernels&amp;rev=1759830220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T09:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>older-kernels</title>
        <link>http://ssl.webangel.ie/doku.php?id=linux:linux-san:older-kernels&amp;rev=1759830220&amp;do=diff</link>
        <description>Older Kernels

Details fo the HBAs was available under
/proc/scsi/qlxxx  #for Qlogic cards
/proc/scsi/lpfc   #for Emulex cards

you would find to numbered files that indicate the PCI slot that the card was sitting on. 

so for example


cat /proc/scsi/ql23xx/1 
QLogic PCI to Fibre Channel Host Adapter for QLA2460:
        Firmware version:  4.00.23, Driver version 7.07.05
Entry address = f888d060

Request Queue = 0x37280000, Response Queue = 0x37270000
Request Queue count= 512, Response Queue co…</description>
    </item>
</rdf:RDF>
