1TARGETS(5) BSD File Formats Manual TARGETS(5)
2
4 targets — configuration file for iSCSI targets
5
7 targets
8
10 The targets file describes the iSCSI storage which is presented to iSCSI
11 initiators by the iscsi-target(8) service. A description of the iSCSI
12 protocol can be found in Internet Small Computer Systems Interface RFC
13 3720.
14 Each line in the file (other than comment lines that begin with a ‘#’)
16 specifies an extent, a device (made up of extents or other devices), or a
17 target to present to the initiator.
18 Each definition, an extent, a device, and a target, is specified on a
20 single whitespace delimited line.
21 The extent definition specifies a piece of storage that will be used as
23 storage, and presented to initiators. It is the basic definition for an
24 iSCSI target. Each target must contain at least one extent definition.
25 The first field in the definition is the extent name, which must begin
26 with the word “extent” and be followed by a number. The next field is
27 the file or NetBSD device which will be used as persistent storage. The
28 next field is the offset (in bytes) of the start of the extent. This
29 field is usually 0. The fourth field in the definition is the size of
30 the extent. The basic unit is bytes, and the shorthand KB, MB, GB, and
31 TB can be used for kilobytes (1024 bytes), megabytes (1024 kilobytes),
32 gigabytes (1024 megabytes), and terabytes (1024 gigabytes) respectively.
33 The device definition specifies a LUN or device, and is made up of
35 extents and other devices. It is possible to create hierarchies of
36 devices using the device definition. The first field in the definition
37 is the device name, which must begin with the word “device” and be fol‐
38 lowed by a number. The next field is the type of resilience that is to
39 be provided by the device. For simple devices, RAID0 suffices. Greater
40 resilience can be gained by using the RAID1 resilience field. Following
41 the resilience field is a list of extents or other devices. Large
42 devices can be created by using multiple RAID0 extents, in which case
43 each extent will be concatenated. Resilient devices can be created by
44 using multiple RAID1 devices or extents, in which case data will be writ‐
45 ten to each of the devices or extents in turn. If RAID1 resilience is
46 used, all the extents or sub-devices must be the same size. Please note
47 that RAID1 recovery is not yet supported by the iscsi-target(8) utility.
48 An extent or sub-device may only be used once.
49 The target definition specifies an iSCSI target, which is presented to
51 the iSCSI initiator. Multiple targets can be specified. The first field
52 in the definition is the target name, which must begin with the word
53 “target” and be followed by a number. The next field is a selector for
54 whether the storage should be presented as writable, or merely as read-
55 only storage. The field of “rw” denotes read-write storage, whilst “ro”
56 denotes read-only storage. The next field is the device or extent name
57 that will be used as persistent storage for this target. The fourth
58 field is a slash-notation netmask which will be used, during the discov‐
59 ery phase, to control the network addresses to which targets will be pre‐
60 sented. The magic values “any” and “all” will expand to be the same as
61 “0/0”. If an attempt is made to discover a target which is not allowed
62 by the netmask, a warning will be issued using syslog(3) to make adminis‐
63 trators aware of this attempt. The administrator can still use tcp wrap‐
64 per functionality, as found in hosts_access(5) and hosts.deny(5) to allow
65 or deny discovery attempts from initiators as well as using the inbuilt
66 netmask functionality.
67
69 /etc/iscsi/targets the list of exported storage targets
70
72 syslog(3), hosts_access(5), hosts.deny(5), iscsi-target(8)
73
75 The targets file first appeared in NetBSD 4.0.
76BSD February 16, 2006 BSD