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

Edward Tomasz Napierała trasz at freebsd.org
Thu Oct 17 11:15:02 UTC 2013


Wiadomość napisana przez Outback Dingo <outbackdingo at gmail.com> w dniu 17 paź 2013, o godz. 03:11:

[..]

> 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

[..]

> 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 ??

Not really, because in some cases that's exactly what you want.  That's why
ctld(8) only warns about it when running with debugging enabled.



More information about the freebsd-current mailing list