Thanks for coming back rarylson!
It seems no one realized this implicitly fixed this issue when the changes were
made.
Closing the bug as fix released (since artful).
** Changed in: tgt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a mem
Hi everyone.
It seems like the TGT bug (when stopping, reloading or restarting the
TGT deamon) is solved in Ubuntu Artful (17.10). I did not make tests,
but now TGT uses the upstream init.d script or the TGT systemd config
file (both of them address all of the previous described problems).
The co
Hi Serge Hallyn,
I run some new tests and, in short, the problem I found is actually three
problems (maybe this bug should be broke in three).
I will summarize the problems I found:
- Tgtd breaks when it receives a SIGHUP;
- When we send a SIGHUP to tgtd (`reload tgt`), the deamon stops (and
Thanks for taking the time to report this bug. It doesn't look like
it's been addressed upstream at all (no catching of sighup going on in
git head).
** Changed in: tgt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: tgt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294267
Title:
tgt doesn't export some LUNs after a reload operation (SIGHUP)
To manage no
In the attachment, I implemented a fix for the `restart` and
`stop+start` bug.
It's a poor fix, but it may help.
Unfortunately, I don't found any fix for the reload method, since
upstart (in Ubuntu 12.04) always send a SIGHUP signal to the deamon.
** Attachment added: "tgt.override"
https:/
I discovered that, although sending a SIGHUG signal to TGT (using the
`reload tgt` command) doesn't works, I can correctly "reload" TGT using
the following command:
tgt-admin --update ALL
I know upstart has the option to change the signal send to a deamon.
However, if we could change the `rel
Sometimes, the restart operation doesn't works also:
$ tgt-admin --dump
default-driver iscsi
backing-store /dev/vg_vmware/vmware_4
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
backing-store /dev/vg_vmware/vmware_3
initiator-address 19
I think the problem can be related to this fact: the TGT daemon don't
add a block storage to a LUN if some process was accessing it.
The following command show another operation in which a similar problem
occours:
# All block storage added to the targets
$ tgt-admin --dump | grep -o "backing-stor
