[[Plugins] iSCSI GUI and ISCSI Target]

On 4/14/2021 at 8:40 AM, SimonF said:

Which of the iscsi plugins are you using?

 

Another plugin should not be making changes to another,  Also changing the config would not update the actual status.

 

It would down to the user to make sure the device is available.

 

On 4/14/2021 at 9:18 AM, ich777 said:

@stinger2k I also agree with @SimonF that a plugin should never change another plugin and it's up to the user so that he makes sure that the device is available.

 

If it would be done like this the main problem is if a user selects by accident a device that has a partition or something mounted he can delete all of the contents of this device.

 

The Problem is that drive partition is mounted by unassigned devices (is the automatic Setting for known filesystems) before "targetcli" can load it as a "block"-device. So targetcli exited with "Drive is Busy..."

So maybe it would be better to passthrough error-message of targetcli to WebUi or check if the marked device is mounted and unmount "before" targetcli is called, only thoughts to make the plugin more comfortable, because no message of targetcli is piped to WebUi.

[[Plugins] iSCSI GUI and ISCSI Target]

There´s a problem with Unassigned Devices Plugin and this Plugin, when i want to create Blockdevice as a iSCSI-Volume it didn´t recognize if a Partition in it is currently mounted or not, so targetcli can´t create Block-Volume because drive is in busy state as long it´s mounted.

Please fix that.

 

Simple check on this file would do it if there´s a "yes" entry and set it to "false".