http://bugzilla.suse.com/show_bug.cgi?id=975604 http://bugzilla.suse.com/show_bug.cgi?id=975604#c3 Lee Duncan <lduncan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lduncan@suse.com) | --- Comment #3 from Lee Duncan <lduncan@suse.com> --- (In reply to Gabriele Mohr from comment #2)

Verified that in IscsiLioData.rb always "iblock_0" resp. "fileio_0" is used for TCM_HBA/DEV.

Lee, if this is deprecated, what's the correct approach here?

No, the lio-utils are not yet deprecated, although the targetcli interface is much easier to use for customers. Not much development goes on for lio-utils (none?), but they are still used and will continue be in SLE 12. But yast probably should not reuse fileio_0 (for file backends) or iblock_0 (for block device backends). This essentially becomes the "HBA" for the virtual device. It is recommended that each device have it's own HBA. For light/normal usage, it probably doesn't matter, but for startup, you can have race conditions with multiple devices per HBA. So you should probably use "fileio_0", "fileio_1", "fileio_2", ... (for file backends), and similar for block backends. So I would consider this a YaST2 bug, but of lower priority for now? Personally, I would like to see us to to using targetcli instead of lio-utils in YaST, but we are currently evaluating replacing targetcli with targetcli-fb, which is the current "best" API, so no use changing YaST for now. Setting NEEDSINFO back to Gabi. -- You are receiving this mail because: You are on the CC list for the bug.