Public bug reported:
Sometime, after run a `reload tgt`, some LUNs aren't correctly added to
the targets.
The error will be reproduced above:
$ tgt-admin --dump
default-driver iscsi
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_4>
backing-store /dev/vg_vmware/vmware_4
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_3>
backing-store /dev/vg_vmware/vmware_3
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_2>
backing-store /dev/vg_vmware/vmware_2
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_1>
backing-store /dev/vg_vmware/vmware_1
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_5>
backing-store /dev/vg_vmware/vmware_5
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
Now, we'll send a SIGHUP signal to tgt:
$ reload tgt
# run `kill -SIGHUP $TGT_ROOT_PID` have the same behavior
$ tgt-admin --dump
default-driver iscsi
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_4>
backing-store /dev/vg_vmware/vmware_4
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_3>
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_2>
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_1>
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
<target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_5>
backing-store /dev/vg_vmware/vmware_5
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
</target>
Now, some target LUNs weren't correcty attached to the target
(/dev/vg_vmware/vmware_1, /dev/vg_vmware/vmware_2 and
/dev/vg_vmware/vmware_3 in my example).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: tgt 1:1.0.17-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Tue Mar 18 14:57:37 2014
MarkForUpload: True
SourcePackage: tgt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: tgt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1294267
Title:
tgt doesn't export some LUNs after a reload operation (SIGHUP)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1294267/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
