tgtd target will not start unless it's configured with "allow-in-use yes"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tgt (Ubuntu) |
Fix Released
|
Medium
|
Chris Cheney | ||
Maverick |
Fix Released
|
Medium
|
Chris Cheney |
Bug Description
Binary package hint: tgt
tgt-admin will not start a target unless we specify the "allow-in-use yes" directive in the target declaration. It complains that the device is in use, although I am positive it is not. Specifying "allow-in-use yes" is not recommended, and doing so is not really satisfactory.
ubuntu@
<target iqn.2005-
backing-store /dev/sda
write-cache off
# allow-in-use yes
</target>
ubuntu@
ubuntu@
# default-driver not defined, defaulting to iscsi.
# Adding target: iqn.2005-
tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.2005-
# Device /dev/sda is used (already tgtd target?).
# Run 'lsof /dev/sda' to see the details.
# Skipping device /dev/sda - it is in use.
# You can override it with --force or 'allow-in-use yes' config option.
# Note - do so only if you know what you're doing, you may damage your data.
tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
ubuntu@
Target 1: iqn.2005-
System information:
Driver: iscsi
State: ready
I_T nexus information:
LUN information:
LUN: 0
Type: controller
SCSI ID: IET 00010000
SCSI SN: beaf10
Size: 0 MB
Online: Yes
Backing store type: rdwr
Backing store path: None
Account information:
ACL information:
ALL
ubuntu@
ubuntu@
Changed in tgt (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Chris Cheney (ccheney) |
importance: | Undecided → Medium |
Changed in tgt (Ubuntu Maverick): | |
milestone: | none → maverick-alpha-3 |
I am also positive no other tgtd process where running at the same time.