istgt requires a restart everytime LUNs are changed, which is very cruel.
Also any connectivity issue very easily causes client node to remount as read only, for unknown reason.
Therefore, we are possibly changing the iSCSI daemon to another one within the next 48hrs which was noted to handle errors much more gracefully in tests done earlier.
istgt was chosen because it was the daemon of choice in some enterprise solutions and we already had some experience with istgt.
Things are still a bit work in progress, and i'm sorry for the issues, this is quite a bit of research and development as this kind of usage case isn't just happening elsewhere the way we are doing things.
Monday, July 15, 2013
