Difference between revisions of "ISCSI Initiator"

From ArchWiki
Jump to: navigation, search
m (+ i18n box)
m (done right.. should stop editing, today is not my day)
Line 1: Line 1:
 
[[Category:Storage (English)]]
 
[[Category:Storage (English)]]
 
[[Category:Networking (English)]]
 
[[Category:Networking (English)]]
{{i18n|ISCSI Target}}
+
{{i18n|ISCSI Initiator}}
  
 
{{Article summary start}}
 
{{Article summary start}}

Revision as of 17:12, 11 October 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Summary help replacing me
How to access an iSCSI Target with an initiator.
Series
iSCSI Target
iSCSI Initiator
Related
iSCSI Boot

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.