Difference between revisions of "ISCSI Initiator"

From ArchWiki
Jump to: navigation, search
(Using the Tools: logout + node info)
m (category at top due to arch wiki style (though I don't know if this is good); remove triple newlines and trailing dots.)
Line 1: Line 1:
 +
[[Category:Storage (English)]]
 +
[[Category:Networking (English)]]
 +
 
{{Article summary start}}
 
{{Article summary start}}
 
{{Article summary text|How to access an iSCSI Target with an initiator.}}
 
{{Article summary text|How to access an iSCSI Target with an initiator.}}
Line 14: Line 17:
 
The preferred initiator is [http://open-iscsi.org/ Open-iSCSI] as of 2011. An older initiator, [http://sourceforge.net/projects/linux-iscsi/ Linux-iSCSI], was merged with Open-iSCSI.
 
The preferred initiator is [http://open-iscsi.org/ Open-iSCSI] as of 2011. An older initiator, [http://sourceforge.net/projects/linux-iscsi/ Linux-iSCSI], was merged with Open-iSCSI.
 
Linux-iSCSI should not be confused with linux-iscsi.org, the website for the LIO [[iSCSI Target|target]].
 
Linux-iSCSI should not be confused with linux-iscsi.org, the website for the LIO [[iSCSI Target|target]].
 
  
 
== Setup With Open-iSCSI ==
 
== Setup With Open-iSCSI ==
Line 24: Line 26:
 
At the server (target) you might need to include the client iqn from {{Filename|/etc/iscsi/initiatorname.iscsi}} in the acl configuration.
 
At the server (target) you might need to include the client iqn from {{Filename|/etc/iscsi/initiatorname.iscsi}} in the acl configuration.
  
After both steps are finished you should be able to start the initiator with {{Cli|# /etc/rc.d/open-iscsi start}}.
+
After both steps are finished you should be able to start the initiator with {{Cli|# /etc/rc.d/open-iscsi start}}
You can see the current sessions with {{Cli|# /etc/rc.d/open-iscsi status}}.
+
You can see the current sessions with {{Cli|# /etc/rc.d/open-iscsi status}}
 
You might want to include {{Codeline|open-iscsi}} in your [[rc.conf#Daemons]].
 
You might want to include {{Codeline|open-iscsi}} in your [[rc.conf#Daemons]].
  
Line 61: Line 63:
 
== See also ==
 
== See also ==
 
* [[iSCSI Boot]] Booting Arch Linux with / on an iSCSI target.
 
* [[iSCSI Boot]] Booting Arch Linux with / on an iSCSI target.
 
[[Category:Storage (English)]]
 
[[Category:Networking (English)]]
 

Revision as of 17:09, 11 October 2011

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary heading Template:Article summary wiki Template:Article summary end

With Wikipedia:iSCSI you can access storage over an IP-based network.

The exported storage entity is the target and the importing entity is the initiator.

The preferred initiator is Open-iSCSI as of 2011. An older initiator, Linux-iSCSI, was merged with Open-iSCSI. Linux-iSCSI should not be confused with linux-iscsi.org, the website for the LIO target.

Setup With Open-iSCSI

Even Template:Package AUR is not in the official repositories, so you need to build it from AUR.

Using the Daemon

You only have to include the IP of the target as Template:Codeline in Template:Filename at the client.

At the server (target) you might need to include the client iqn from Template:Filename in the acl configuration.

After both steps are finished you should be able to start the initiator with Template:Cli You can see the current sessions with Template:Cli You might want to include Template:Codeline in your rc.conf#Daemons.

Using the Tools

Template:Codeline has to be running.

Target discovery

Template:Cli

Delete obsolete targets

Template:Cli

Login to available targets

Template:Cli or login to specific target Template:Cli

logout: Template:Cli

Info

For running session Template:Cli For the known nodes Template:Cli

Online resize of volumes

If the iscsi blockdevice contains a partitiontable, you will not be able to do an online resize. In this case you have to unmount the filesystem and alter the size of the affected partition.

  1. Rescan active nodes in current session Template:Cli
  2. If you use multipath, you also have to rescan multipath volume information. Template:Cli
  3. Finally resize the filesystem. Template:Cli

Tips

You can also check where the attached iSCSI devices are located in the /dev tree with Template:Codeline.

See also

  • iSCSI Boot Booting Arch Linux with / on an iSCSI target.