|
From: Bart V. A. <bva...@ac...> - 2011-06-11 10:29:42
|
On Sat, Jun 11, 2011 at 11:52 AM, Matteo Tescione <ma...@rm...> wrote:
>
> i'm trying to use the new fantastic scst init script but it fails:
>
> [root@nas1 default]# /etc/init.d/scst start
> Loading and configuring SCST [FAILED]
> Collecting current configuration..
>
> FATAL: Received the following error:
>
> groups(): Driver '' is not available
>
>
>
> Config is as simple as possible:
> # Automatically generated by SCST Configurator v2.0.0.
> HANDLER vdisk_fileio {
> DEVICE SDD {
> filename /dev/sdd
> }
> }
> TARGET_DRIVER ib_srpt {
> TARGET ib_srpt_target_0 {
> enabled 1
> LUN 0 SDD
> }
> }
> TARGET_DRIVER iscsi {
> enabled 1
> TARGET iqn.2011-01.com.openfiler:RMnet-2tera {
> QueuedCommands 16
> rel_tgt_id 2
> enabled 1
> LUN 0 SDD
> }
> }
>
>
> And scstadmin config validation works fine:
> [root@nas1 default]# modprobe scst
> [root@nas1 default]# modprobe scst_vdisk
> [root@nas1 default]# modprobe ib_srpt
> [root@nas1 default]# modprobe iscsi_scst
> [root@nas1 default]# scstadmin -check_config /etc/scst.conf
>
> Collecting current configuration: done.
>
> -> Checking configuration file '/etc/scst.conf' for errors.
> -> Done, 0 warnings found.
>
>
> All done.
> [root@nas1 default]#
>
>
>
> Am I missing something obvious? or is the init script having some trouble
> loading appropriate modules? what should be inside /etc/default/scst for
> sysfs-mode?
>
The error message "groups(): Driver '' is not available" has been generated
by scstadmin. Apparently a target driver module that should have been loaded
wasn't loaded. I see only one possible cause for this, namely that scst.conf
was hand-edited and some other separator had been used than a single space
in the "TARGET_DRIVER" lines. scst.conf parsing has been relaxed in r3568 on
the trunk. Does that help ?
> P.S. any news on scstadmin ALUA support??
>
Mark maintains scstadmin. I'm not sure how far Mark got with implementing
ALUA support in scstadmin.
Bart.
|