ISCSI target handling is far from being mature

[Buddy]

Hi Guys,

first, many thanks for nas4free. I am using it now for over half a year.
So far, everything worked out quite nice. Also the upgrades went smooth!

The ISCSI target management, though, always gives some headache.
It is not possible to smoothly create, or delete targets when the service is running.
When creating targets, it fires a lot of errors stating that config can not be loded on LU due to LU being
in use. I have read in an other post that it has something to do with the alphabetical order.
If so, this is simply not acceptable. One should be able to create/destroy arbitrary targets on the fly.
When creating targets, I always do not see the new target when browsing from initiators AND
other targets are LOST also in the browse list. There is only one little trick to get it to view without
restarting the service. This is disabling and re-enabling the target, which brings it to show up again.
Though, this then has to be done with all other targets that got lost in the list.

Please note, "save and restart" is NO option as it leads to huge problems and I also experienced
data corruption as this method interrupts all active targets!

I would really very much appreciate if this target handling could be reworked such that it becomes more
stable. I wonder why this has not been reported earlier. Maybe nas4free is only used in smal privat environments
with little amount of services (though, I only have 30 targets).

Thanks a lot and cheers,
Matt

[hvisage]

Or it is just created and left as "Stable" not touched afterwards??

I'm starting to see the same troubles, but my environment is currently quite static, so I don't have this constant stop=start yet.

[STAMSTER]

Even on a big, black boxes of storage like EMC or NetApp you do have service interruption when changing settings...
I guess multi-threaded iSCSI target management in N4F would do the job....