<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.tkc-online.de/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="https://wiki.tkc-online.de/feed.php">
        <title>Wiki - public:iscsi</title>
        <description></description>
        <link>https://wiki.tkc-online.de/</link>
        <image rdf:resource="https://wiki.tkc-online.de/lib/exe/fetch.php/wiki:logo.png" />
       <dc:date>2026-05-06T13:06:09+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:basics?rev=1549440300&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:dm?rev=1717747304&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:fixes?rev=1446122529&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:login?rev=1434120996&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:logout?rev=1717747774&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:lvm?rev=1717746953&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:multipath?rev=1436703873&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.tkc-online.de/doku.php/public:iscsi:relogin?rev=1433585844&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.tkc-online.de/lib/exe/fetch.php/wiki:logo.png">
        <title>Wiki</title>
        <link>https://wiki.tkc-online.de/</link>
        <url>https://wiki.tkc-online.de/lib/exe/fetch.php/wiki:logo.png</url>
    </image>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:basics?rev=1549440300&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-06T08:05:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>basics</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:basics?rev=1549440300&amp;do=diff</link>
        <description>iSCSI basics

In the world of iSCSI the following terms apply:

	*  the iSCSI server is called &#039;iSCSI target&#039;
	*  the iSCSI client is called &#039;iSCSI initiator&#039;.


To keep this wiki compatible to other guides the terms &#039;target&#039; and &#039;initiator&#039; are used as described above.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:dm?rev=1717747304&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-07T08:01:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dm</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:dm?rev=1717747304&amp;do=diff</link>
        <description>DM devices

Device Mapper (abbreviated DM) is the universal technology to access block devices by Linux. For a good overview over DM devices in relation to multipath see here. Ubuntu specific information on DM can be found here. For Debian see here.

All devices described so far are DM devices. Some of the mentioned devices have to be accessed as DM devices only in exceptional cases.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:fixes?rev=1446122529&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-10-29T12:42:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fixes</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:fixes?rev=1446122529&amp;do=diff</link>
        <description>Fix iSCSI login errors

A few solutions for iSCSI log-in errors are known. They are described in the next sections.  

Checking the iSCSI configuration

If the iSCSI login was possible before and the configuration was not changed manually, a misconfiguration will not be very likely - especially when the configuration is distributed by Puppet.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:login?rev=1434120996&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-06-12T14:56:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>login</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:login?rev=1434120996&amp;do=diff</link>
        <description>First connection to iSCSI targets

The standard program for iSCSI management is the administration tool iscsiadm from the package &#039;open-iscsi&#039;. At first check, whether the package &#039;open-iscsi&#039; was installed and its status:
root@kvm55:~# /etc/init.d/open-iscsi status
Current active iSCSI sessions:
iscsiadm: No active sessions.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:logout?rev=1717747774&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-07T08:09:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>logout</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:logout?rev=1717747774&amp;do=diff</link>
        <description>log out of iSCSI targets

For a complete logout of an iSCSI device - especially by keeping other active iSCSI connections -  it is necessary to end all related device connections step by step in the right order. This affects all devices related to the iSCSI connection. Because of the complexity of the logout process and the participation of many different devices a separate section was dedicated to the process.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:lvm?rev=1717746953&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-07T07:55:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lvm</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:lvm?rev=1717746953&amp;do=diff</link>
        <description>LVM devices

The Logical Volume Manager (LVM) is used to create logical partitions on top of local hard disks or iSCSI disks. The use of LVM offers the following advantages:

	*  Isolated partitions for hard disk images and user data can be created on common storage devices.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:multipath?rev=1436703873&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-07-12T12:24:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>multipath</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:multipath?rev=1436703873&amp;do=diff</link>
        <description>Multipath

It is quite common to connect an iSCSI device via two or more network paths for failover reasons. The paths are then joined to one device again with the help of multipath. The iSCSI device must be accessed via the multipath device and must not be accessed via single iSCSI path devices. Otherwise data loss or partition corruption may occur.</description>
    </item>
    <item rdf:about="https://wiki.tkc-online.de/doku.php/public:iscsi:relogin?rev=1433585844&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-06-06T10:17:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>relogin</title>
        <link>https://wiki.tkc-online.de/doku.php/public:iscsi:relogin?rev=1433585844&amp;do=diff</link>
        <description>Connecting to configured iSCSI targets

If the automatic start of iSCSI connections is configured as described, the iSCSI initiator will log into the iSCSI target autmatically as soon as the daemon &#039;open-iscsi&#039; is started.
root@kvm55:~# /etc/init.d/open-iscsi start
…</description>
    </item>
</rdf:RDF>
