Hi Nab, Andy On 4/18/2014 4:16 AM, Nicholas A. Bellinger wrote: > On Thu, 2014-04-17 at 15:29 -0700, Andy Grover wrote: >> <SNIP> >>> I'm not able to reproduce using upstream targetcli code, so I can only >>> assume it's some -fb specific breakage. CC'ing Grover. >> [adding CC targetcli-fb-devel] >> >> Is this really random? it looks to me like all params under the acl are ro. >> >> from iscsi_target_configfs.c:601 >> >> #define NACL_PARAM_ATTR(_name) TF_NACL_PARAM_ATTR_RO(iscsi, _name); >> ^^ >> ... >> >> DEF_NACL_PARAM(ErrorRecoveryLevel); >> >> so yes it's read-only for the acl. >> >> Is it just that you can set ERL in the tpg but not per-acl? And you only >> get the value (instead of "no active iscsi session") when there is a >> session. Is that the problem or something else? Thanks for the explanation. Now this is clear. > This is correct. Only the TPG parameter values can be changed, which > are then propagated down to individual NodeACL parameters as sessions > are created that reference specific InitiatorName entities. > > So yeah, there is nothing random about it. ;) > > --nab Thanks for the explanation. Understood. > Thanks, Arshad -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
