|
From: Mark B. <mar...@gm...> - 2011-07-20 18:15:08
|
Hi On Wed, Jul 20, 2011 at 11:08 AM, Matteo Tescione <ma...@rm...> wrote: > Mark, > > ./ib_srpt_target_0 > ./ib_srpt_target_0/enabled > ./ib_srpt_target_0/sessions > ./ib_srpt_target_0/luns > ./ib_srpt_target_0/luns/mgmt > ./ib_srpt_target_0/ini_groups > ./ib_srpt_target_0/ini_groups/mgmt > ./ib_srpt_target_0/rel_tgt_id > ./ib_srpt_target_0/comment > ./ib_srpt_target_0/addr_method > ./ib_srpt_target_0/io_grouping_type > ./ib_srpt_target_0/cpu_mask > ./ib_srpt_target_0/login_info > > Please consider that the new initd script fails with or without srpt > target. > Executing sh -x, we found that the parser is correctly loading the > appropriate modules, in this case scst, scst_vdisk, iscsi_scst and ib_srpt, > but the scstadmin -config /etc/scst.conf fails with that error. > Please consider too that manual modprobe scst, modprobe scst_vdisk, > modprobe iscsi_scst, modprobe ib_srpt, daemon iscsi_scstd and scstadmin > -config /etc/scst.conf works just fine. > > Many thanks, > -- > Ok, let me make sure I have this correct. The problem line is the clear_config line, correct? So, if you manually modprobe and scstadmin -config, what happens when you manually -clear_config? - Mark. |