LIO

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m
m
Line 58: Line 58:
* [[Howto#Start_target_core_mod|HOWTO]]: starting the Target.
* [[Howto#Start_target_core_mod|HOWTO]]: starting the Target.
-
[[RisingTide Systems]] makes available upon request and for free [[RTSadmin]], a comprehensive, powerful, yet easy storage management tool that can easily handle even complex LIO installations.
+
[[RisingTide Systems]] makes available upon request and for free [[RTSadmin]], a comprehensive, powerful, yet easy storage management tool that can efficiently handle even complex LIO installations.
Lastly, the Target engine configuration is mapped into [[Target/configFS]], where it can be configured manually from user space by using inter- and intra-module symbolic links.
Lastly, the Target engine configuration is mapped into [[Target/configFS]], where it can be configured manually from user space by using inter- and intra-module symbolic links.
Line 89: Line 89:
* {{anchor|MPIO}} '''Multipath I/O''' ('''MPIO'''): A method by which data can take multiple redundant paths between a server and storage.
* {{anchor|MPIO}} '''Multipath I/O''' ('''MPIO'''): A method by which data can take multiple redundant paths between a server and storage.
* {{anchor|Network Portal}} '''Network Portal''': The combination of an iSCSI Endpoint with an IP address plus a TCP port. The TCP port number for the iSCSI protocol defined by IANA is 3260.
* {{anchor|Network Portal}} '''Network Portal''': The combination of an iSCSI Endpoint with an IP address plus a TCP port. The TCP port number for the iSCSI protocol defined by IANA is 3260.
-
* {{anchor|OUI}} '''Organizationally Unique Identifier''' ('''OUI''') is a 24-bit number that is purchased from the IEEE Registration Authority. This identifier uniquely identifies a vendor, manufacturer, or other organization (referred to by the IEEE as the '''“assignee”''') globally or worldwide and effectively reserves a block of each possible type of derivative identifier (such as MAC addresses, group addresses, Subnetwork Access Protocol protocol identifiers, etc.) for the exclusive use of the assignee, see [http://en.wikipedia.org/wiki/Organizationally_Unique_Identifier OUI Wikipedia entry]. The OUI is subsequently used by the assignee to create particular instances of these identifiers for various purposes, such as the identification of a particular piece of equipment.
+
* {{anchor|OUI}} '''Organizationally Unique Identifier''' ('''OUI''') is a 24-bit number that is purchased from the IEEE Registration Authority. This identifier uniquely identifies a vendor, manufacturer, or other organization (referred to by the IEEE as the “assignee”) globally or worldwide and effectively reserves a block of each possible type of derivative identifier (such as MAC addresses, group addresses, Subnetwork Access Protocol protocol identifiers, etc.) for the exclusive use of the assignee, see [http://en.wikipedia.org/wiki/Organizationally_Unique_Identifier OUI Wikipedia entry]. The OUI is subsequently used by the assignee to create particular instances of these identifiers for various purposes, such as the identification of a particular piece of equipment.
* {{anchor|SAM}} '''SCSI Architectural Model''' ('''SAM'''): A document that describes the behavior of SCSI in general terms, allowing for different types of devices communicating over various media.
* {{anchor|SAM}} '''SCSI Architectural Model''' ('''SAM'''): A document that describes the behavior of SCSI in general terms, allowing for different types of devices communicating over various media.
* {{anchor|Target}} '''Target''': The receiving end of a SCSI session, typically a device such as a disk drive, tape drive, or scanner.
* {{anchor|Target}} '''Target''': The receiving end of a SCSI session, typically a device such as a disk drive, tape drive, or scanner.

Revision as of 10:04, 28 November 2010

The Target is the generic multiprotocol target engine of LIO.

Contents

Overview

Target
Logo
RisingTide Systems
Generic Target Engine
Original author(s) Nicholas Bellinger
Developer(s) RisingTide Systems LLC
Initial release March 15, 2007 (2007-03-15)
Stable release 3.5.0 / September 19, 2010;
9 years ago
 (2010-09-19)
Preview release 4.0.0-rc5 / October 18, 2010;
8 years ago
 (2010-10-18)
Development status Production
Written in C
Operating system Linux
Type SCSI Target engine
License GNU General Public License
Website datera.io
SCSI Portal Group architecture overview.
LIO iSCSI architecture diagram.
SCSI standards diagram.

The LIO target (target_core_mod.ko) is the generic multiprotocol target engine of LIO.

Architecturally, it can run on a number of different Linux environments, allows access to storage objects from the SCSI, block and VFS subsystems (such as Target/PSCSI, Target/IBLOCK, Target/FILEIO, Target/RAMDISK), and it operates with a number of protocol-specific fabric modules (such as iSCSI, FCoE, Fibre Channel, InfiniBand).

LIO supports advanced iSCSI features, such as Persistent Reservations, ALUA, MC/S and ERL=2.

Standards compliance

The Target supports the SCSI-3 standard for storage devices from Target/IBLOCK, Target/FILEIO, Target/PSCSI, and Target/RAMDISK subsystem plugins. Some of the most notable functionality includes Persistent Reservations (PR) and ALUA, which have been implemented in LIO 3.0, following the SPC-4 standard.

SCSI-3 and greater revisions are supported using the Target/PSCSI subsystem plugin for Linux/SCSI passthrough, but only from control CDBs capable by the device firmware. Linux/SCSI block devices can take advantage of PR and ALUA functionality via the tcm_loop loopback device.

Setup

The LIO 3.0 CLI manual describes a simple userspace shell (lio-utils) for LIO v3.0 (Target+iSCSI). It also describes how to setup a number of different subsystem storage object backstores for LIO LUN endpoints:

RisingTide Systems makes available upon request and for free RTSadmin, a comprehensive, powerful, yet easy storage management tool that can efficiently handle even complex LIO installations.

Lastly, the Target engine configuration is mapped into Target/configFS, where it can be configured manually from user space by using inter- and intra-module symbolic links.

Specifications

The following specifications are available as T10 Working Drafts:

Glossary

Timeline

Timeline of the LinuxIO
Release Details 2011 2012 2013 2014 2015
123456789101112 123456789101112 123456789101112 123456789101112 123456789101112
4.x Version 4.0 4.1
Feature LIO Core Loop back FCoE iSCSI Perf SRP
CM WQ FC
USB
1394
vHost Perf Misc 16 GFC iSER Misc VAAI Misc DIF Core
NPIV
DIF iSER DIF FC vhost TCMU Xen Misc Misc virtio 1.0 Misc NVMe OF
Linux 2.6.38 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22

Wikipedia entries

RFCs

See also

Notes

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense