[SOLVED] Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2

[Outback Dingo]

On Fri, Oct 11, 2013 at 11:52 PM, Miguel C. <miguelmclara at gmail.com> wrote:

> I updated to alpha5 it is indeed removed.
>
> Thanks
>
>
> "Edward Tomasz Napierała" <trasz at FreeBSD.org> wrote:
> >Dnia 11 paź 2013 o godz. 13:15 "Mike C." <miguelmclara at gmail.com>
> >napisał(a):
> >
> >>
> >>> On 10/11/13 09:24, Edward Tomasz Napierała wrote:
> >>>> Wiadomość napisana przez Mike C. w dniu 10 paź 2013, o godz. 23:41:
> >>>> Hi,
> >>>>
> >>>> I'm running Alpha-2 and wanted to test with iscsi but it seems I
> >can't
> >>>> start iscsid.
> >>>>
> >>>>
> >>>> $ sudo service iscsid onerestart
> >>>> kldload: can't load iscsi: Exec format error
> >>>> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi
> >>>> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid
> >>>>
> >>>>
> >>>> dmesg shows:
> >>>> interface icl.1 already present in the KLD 'kernel'!
> >>>> linker_load_file: Unsupported file type
> >>>
> >>> Do you have "device ctl" in your kernel config?  If so,
> >>> either remove it (ctl.ko module is automatically loaded
> >>> by ctladm), or add "device iscsi".
> >>
> >> device          ctl             # CAM Target Layer
> >>
> >> Seems that GENERIC has it by default! I'll remove and recompile!
> >
> >Actually, it got removed from GENERIC in 10 some time ago.
>

Ive actually noticed what i feel is an anomaly with ctladm... i can
literally
run ctladm create -b block -o file=/luns/LUN0 numerous times...... and
create a new LUN
every time, using the same file.

ctladm devlist
LUN Backend       Size (Blocks)   BS Serial Number    Device ID
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:       block
device type:   0
LUN size:      10485760 bytes
blocksize      512 bytes
LUN ID:        0
Serial Number: MYSERIAL   0
Device ID;     MYDEVID   0
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:       block
device type:   0
LUN size:      10485760 bytes
blocksize      512 bytes
LUN ID:        1
Serial Number: MYSERIAL   1
Device ID;     MYDEVID   1
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:       block
device type:   0
LUN size:      10485760 bytes
blocksize      512 bytes
LUN ID:        2
Serial Number: MYSERIAL   2
Device ID;     MYDEVID   2
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:       block
device type:   0
LUN size:      10485760 bytes
blocksize      512 bytes
LUN ID:        3
Serial Number: MYSERIAL   3
Device ID;     MYDEVID   3
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:       block
device type:   0
LUN size:      10485760 bytes
blocksize      512 bytes
LUN ID:        4
Serial Number: MYSERIAL   4
Device ID;     MYDEVID   4
san: ~ # ctladm devlist -v
LUN Backend       Size (Blocks)   BS Serial Number    Device ID
  0 block                 20480  512 MYSERIAL   0     MYDEVID   0
      lun_type=0
      num_threads=14
      file=/mnt/extent6
  1 block                 20480  512 MYSERIAL   1     MYDEVID   1
      lun_type=0
      num_threads=14
      file=/mnt/extent6
  2 block                 20480  512 MYSERIAL   2     MYDEVID   2
      lun_type=0
      num_threads=14
      file=/mnt/extent6
  3 block                 20480  512 MYSERIAL   3     MYDEVID   3
      lun_type=0
      num_threads=14
      file=/mnt/extent6
  4 block                 20480  512 MYSERIAL   4     MYDEVID   4
      lun_type=0
      num_threads=14
      file=/mnt/extent6

notice the same file is used for each LUN...... it appears that ctladm
never checks for a LUN using the same file..... or zpool for that
matter....... anyway we can "correct" said behavior ??


>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>