Main Page

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
Line 6: Line 6:
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to {{LIO servername}},</div>
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to {{LIO servername}},</div>
<div style="top:+0.2em; font-size:95%;">the generic Linux SCSI Target wiki.</div>
<div style="top:+0.2em; font-size:95%;">the Linux SCSI Target wiki.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles, [[Special:Statistics|{{NUMBEROFVIEWS}}]] pageviews</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles, [[Special:Statistics|{{NUMBEROFVIEWS}}]] pageviews</div>

Revision as of 00:06, 17 November 2013

Welcome to Linux-IO,
the Linux SCSI Target wiki.
100 articles, 121,904,219 pageviews


LIO (Linux-IO) is the standard open-source SCSI target for block storage in Linux. It supports all prevalent storage fabrics, including Fibre Channel (QLogic), FCoE, iEEE 1394, iSCSI, iSER (Mellanox InfiniBand), SRP (Mellanox InfiniBand), USB, vHost, etc.

The advanced feature set of the LinuxIO has made it the SCSI target of choice for many storage array vendors, for instance allowing them to achieve VMware® Ready certifications. Native support for LIO in QEMU/KVM, libvirt, and OpenStack™ (setup, code) makes it an attractive storage option for cloud deployments.

LIO includes targetcli, a management shell and API with a single namespace for all storage objects.

LIO and targetcli are developed by Datera, Inc., a data storage systems and software company located in Mountain View in the Silicon Valley.



Fabric Modules implement the protocols to transmit data over diverse fabrics, providing transport media independence.


Backstores implement the methods to access data on devices, providing storage media independence.


The LinuxIO engine implements the generic SCSI semantics.

Advanced SCSI feature set

Compatibility and certifications

LIO works with Initiators of the following operating systems:

LIO enables VMware Ready certifications (incl. vSphere™ 5). It also passes the Microsoft Windows® Server 2008 / R2 Failover Cluster compatibility test suites.


targetcli provides the fabric agnostic single-node management shell for LIO. targetcli aggregates and exports all LIO SAN functionality via the RTSlib library and API [HTML][PDF].


LIO integrates LIO and targetcli into a single-node Hybrid Storage operating system (Template:OS Admin Manual). LIO supports VMware Ready certification, including VMware vSphere™ 5.

An LIO subscription provides access to additional LIO packages and update services.

High availability and clustering

LIO is designed from ground up to support highly available and cluster storage:
  • Deeply embedded high availability (Network RAID1)
  • Scale-out clusters and disaster recovery solutions


The Core-iSCSI Initiator is a high-end iSCSI Initiator that resolves a number of known issues with the Open-iSCSI standard Linux Initiator.

Core-iSCSI is available on Linux and Windows®, and it has been ported to a wide range of platforms and devices, including:

Datera, Inc. ported OCFS2 onto the Nokia Internet Tablets on top of the Core-iSCSI Initiator.

RTS Director

RTS Director is a distributed, highly-available cluster management framework. It comprises a shell, active library and API. The active library and API provide an extensible platform with a unified namespace to manage complex functionality, such as high-availability and cluster striping. The shell offers location-transparent access to all objects in the SAN. New functionality and devices can be added via plugin-modules.

RTS Director provides zero configuration. It is based on a symmetrically distributed architecture - there is no single point of failure, no cluster controller, no central database, etc. Nodes running the RTS Director automatically discover and join the cluster when coming up (demo video).

See also

Personal tools
Google AdSense