Linux iSCSI Target (TCM) - Revision history

Darkfader: add fibrechannel target info

2026-01-12T07:36:21Z

add fibrechannel target info

@@ Line 81: / Line 81: @@
 Errors don't simply appear, but e.g. if you're missing a HBA on boot, these settings
 will not be loaded and thus not be in the configuration upon save.
 [[Category:Storage]]

Bt129 at 04:39, 5 July 2021

2021-07-05T04:39:20Z

← Older revision		Revision as of 04:39, 5 July 2021
Line 79:		Line 79:
	targetcli creates a config backup if you exit, meaning you might lose the working		targetcli creates a config backup if you exit, meaning you might lose the working
	config at the time. So better to be prepared.		config at the time. So better to be prepared.
	Errors don't simply appear, but i.e. if you're missing a HBA on boot, these settings		Errors don't simply appear, but e.g. if you're missing a HBA on boot, these settings
	will not be loaded and thus not be in the configuration upon save.		will not be loaded and thus not be in the configuration upon save.

	[[Category:Storage]]		[[Category:Storage]]

Jirib79 at 20:38, 15 March 2021

2021-03-15T20:38:42Z

← Older revision		Revision as of 20:38, 15 March 2021
Line 12:		Line 12:

	# targetcli		# targetcli
	~~Welcome to the targetcli shell::~~		/>
	~~Copyright (c) 2011 by RisingTide Systems LLC.~~

	~~For help on commands, type 'help'.~~

	/> ls		/> ls
	o- / ..................................................................... [...]		o- / ..................................................................... [...]

Jirib79 at 20:36, 15 March 2021

2021-03-15T20:36:54Z

← Older revision		Revision as of 20:36, 15 March 2021
Line 1:		Line 1:
	~~Since~~ kernel ~~2.6~~.~~38 Linux has a new generic Target Core module, merged from LIO [~~[http://linux-iscsi.org~~/wiki/Main_Page~~]~~], and since 3~~.~~1 there is iSCSI support~~. ~~This how-to quickly explains how to use it~~.		{{Note\|TCM is another name for LinuxIO (LIO), an in-kernel iSCSI target (server). [http://linux-iscsi.org LIO] is the standard open source multiprotocol SCSI target for Linux. LIO replaced the STGT (SCSI Target) framework as the standard unified storage target in Linux with Linux kernel version 2.6.38 and later.}}

	Install the utilities to configure Target Core:		Install the utilities to configure Target Core:

Nirsof: Starting targetcli fail with "g-io-error-quark: Could not connect: No such file or directory" if dbus service is not running. Start dbus before targetcli, and change service order for consistency.

2020-11-11T17:37:45Z

Starting targetcli fail with "g-io-error-quark: Could not connect: No such file or directory" if dbus service is not running. Start dbus before targetcli, and change service order for consistency.

← Older revision		Revision as of 17:37, 11 November 2020
Line 4:		Line 4:

	# apk add targetcli		# apk add targetcli
			# rc-update add dbus
	# rc-update add targetcli		# rc-update add targetcli
	# ~~rc-update add~~ dbus		# service dbus start
	# service targetcli start		# service targetcli start
	~~# service dbus start~~

	In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):		In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):

Bogon at 07:55, 6 February 2020

2020-02-06T07:55:27Z

← Older revision		Revision as of 07:55, 6 February 2020
Line 55:		Line 55:
	Now you have to tell Target Core to use the previously create backstore for the target now created:		Now you have to tell Target Core to use the previously create backstore for the target now created:

	../tpg1~~> cd~~ luns		/iscsi> cd iqn.2003-01.org.linux-iscsi.rtsnode1.x8664:sn.83a8cde7aca8/tpg1/luns
	../tpg1/luns> create lun=0 storage_object=/backstores/blockio/block0		../tpg1/luns> create lun=0 storage_object=/backstores/blockio/block0
	Successfully created LUN 0.		Successfully created LUN 0.

Bogon: Requires dbus

2020-02-06T07:52:35Z

Requires dbus

← Older revision		Revision as of 07:52, 6 February 2020
Line 5:		Line 5:
	# apk add targetcli		# apk add targetcli
	# rc-update add targetcli		# rc-update add targetcli
	# ~~/etc/init.d/~~targetcli start		# rc-update add dbus
			# service targetcli start
			# service dbus start

	In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):		In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):

Cosmic-leaf: Removed obsolete information.

2013-08-04T16:57:37Z

Removed obsolete information.

← Older revision		Revision as of 16:57, 4 August 2013
Line 1:		Line 1:
	Since kernel 2.6.38 Linux has a new generic Target Core module, merged from LIO [[http://linux-iscsi.org/wiki/Main_Page]], and since 3.1 there is iSCSI support. This how-to quickly explains how to use it.		Since kernel 2.6.38 Linux has a new generic Target Core module, merged from LIO [[http://linux-iscsi.org/wiki/Main_Page]], and since 3.1 there is iSCSI support. This how-to quickly explains how to use it.
	~~Currently the userland utils are available only in Alpine edge/main repository (upcoming Alpine 2.5).~~

	Install the utilities to configure Target Core:		Install the utilities to configure Target Core:

Darkfader: automatically start targetcli and notes about backup.

2012-12-19T15:44:19Z

automatically start targetcli and notes about backup.

← Older revision		Revision as of 15:44, 19 December 2012
Line 5:		Line 5:

	# apk add targetcli		# apk add targetcli
			# rc-update add targetcli
	# /etc/init.d/targetcli start		# /etc/init.d/targetcli start

Line 76:		Line 77:
	Existing file /etc/target/saveconfig.json backed up to saveconfig.json.backup		Existing file /etc/target/saveconfig.json backed up to saveconfig.json.backup
	Configuration saved to /etc/target/saveconfig.json		Configuration saved to /etc/target/saveconfig.json

			For real use, you should always track changes to the saveconfig file and make sure
			(there's a flag for it) to not save config if you are in an error situation. By default,
			targetcli creates a config backup if you exit, meaning you might lose the working
			config at the time. So better to be prepared.
			Errors don't simply appear, but i.e. if you're missing a HBA on boot, these settings
			will not be loaded and thus not be in the configuration upon save.

	[[Category:Storage]]		[[Category:Storage]]

Roger.pau at 11:53, 20 November 2012

2012-11-20T11:53:03Z

← Older revision		Revision as of 11:53, 20 November 2012
Line 5:		Line 5:

	# apk add targetcli		# apk add targetcli
			# /etc/init.d/targetcli start

	In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):		In contrast with plain text files as usual, all configuration is done in ConfigFS via targetcli shell (you can use tab for command auto-completion and "ls" for inspecting current config):