Hi Nab, Randomly my targetcli sets 'ErrorRecoveyLevel' as read only. I have checked the configfs and debugfs they are both mounted with permission of read and write. What surprises me is that the ERL and default_erl under 'tpg1' is fine. It is only the ERL parameter under 'acls/iqn...' which is marked read-only. Could you comment on this please ? Is there a work-around to get over this issue? I have provided the details below. Please let me know if there any other info you require? Thanks, Arshad <snip> /iscsi/iqn.20...t:981fc286f48> get parameter ErrorRecoveryLevel ErrorRecoveryLevel=No Active iSCSI Session [ro] /iscsi/iqn.20...t:981fc286f48> set parameter ErrorRecoveryLevel=2 Parameter ErrorRecoveryLevel is read-only. /iscsi/iqn.20...t:981fc286f48> /iscsi/iqn.20...t:981fc286f48> get attribute default_erl default_erl=2 /iscsi/iqn.20...t:981fc286f48> /iscsi/iqn.20...093081c0/tpg1> pwd /iscsi/iqn.2003-01.org.linux-iscsi.wfs.x8664:sn.a6fd093081c0/tpg1 /iscsi/iqn.20...093081c0/tpg1> get parameter ErrorRecoveryLevel ErrorRecoveryLevel=2 /iscsi/iqn.20...093081c0/tpg1> get attribute default_erl default_erl=2 /iscsi/iqn.20...093081c0/tpg1> # Output from /sys/kernel/config [root@wfsc its]# cat /sys/kernel/config/target/iscsi/iqn.2003-01.org.linux-iscsi.wfs.x8664\:sn.a6fd093081c0/tpgt_1/acls/iqn.1994-05.com.redhat\:981fc286f48/param/ErrorRecoveryLevel No Active iSCSI Session [root@wfsc its]# [root@wfsc log]# mount | grep configfs configfs on /sys/kernel/config type configfs (rw,relatime) [root@wfsc log]# mount | grep debugfs none on /sys/kernel/debug type debugfs (rw,relatime) [root@wfsc log]# [root@wfsc log]# rpm -q --whatprovides /usr/bin/targetcli targetcli-2.1.fb30-1.fc18.noarch [root@wfsc log]# cat /etc/issue Fedora release 18 (Spherical Cow) Kernel \r on an \m (\l) [root@wfsc log]# [root@wfsc log]# uname -a Linux wfsc 3.14.0-rc6 #1 SMP Mon Mar 17 09:07:33 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux [root@wfsc log]# <snip> -- 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
