Re: iscsi crash

[Michael van Elst <mlelstv%serpens.de@localhost>]

On Sun, Jan 05, 2014 at 09:48:13AM +0100, 
6bone%6bone.informatik.uni-leipzig.de@localhost wrote:

> is configured. So I think the kernel is modular. The GENERIC kernel
> does not work because the option 'pseudo-device iscsi' is needed but
> not set in GENERIC.

For amd64 I don't have to add 'pseudo-device iscsi'. When you start
the iscsid, the pseudo-device driver is loaded automatically as
a kernel module.


% sudo iscsid
Password:
% dmesg | tail -1
iscsi: attached.  major = 203
% modstat iscsi
NAME             CLASS      SOURCE     REFS  ADDRESS          SIZE     REQUIRES 
iscsi            driver     filesys    0     ffffffff80c8b000 45332    -
% sudo iscsictl add_send_target -a 10.25.5.4
Added Send Target 1
% sudo iscsictl refresh_targets
OK
% sudo iscsictl list_targets
    1: iqn.2000-01.com.synology:diskstation.name
       2: 169.254.157.182:3260,0
       3: 10.25.5.4:3260,0
    4: iqn.2000-01.com.synology:diskstation.name1
       5: 169.254.157.182:3260,0
       6: 10.25.5.4:3260,0
% sudo iscsictl login -P 3
Created Session 2, Connection 1
% dmesg | tail -8
scsibus1 at iscsi0: 1 target, 16 luns per target
sd1 at scsibus1 target 0 lun 0: <SYNOLOGY, iSCSI Storage, 3.1> disk fixed
sd1: fabricating a geometry
sd1: 20480 MB, 20480 cyl, 64 head, 32 sec, 512 bytes/sect x 41943040 sectors
sd1: fabricating a geometry
dk8 at sd1: sd1a
dk8: 41942976 blocks at 64, type: ffs
sd1: async, 8-bit transfers, tagged queueing
% sudo iscsictl list_sessions
Session 2: Target iqn.2000-01.com.synology:diskstation.name
% sudo iscsictl logout -I 2
OK
% dmesg | tail -3
dk8 at sd1 (sd1a) deleted
sd1: detached
scsibus1: detached
% sudo modunload iscsi
[... takes a while ...]
% dmesg | tail -1
iscsi0: detached
% modstat iscsi
NAME             CLASS      SOURCE     REFS  ADDRESS          SIZE     REQUIRES 
% pkill iscsid
% pgrep iscsid
% 



On other archs, that do not yet support modules, I have added
the pseudo-device like you. But I'm not sure if that already
worked for netbsd-6.

The whole construct of iscsi driver and iscsi daemon is still
flakey. Both parts keep session states, killing iscsid will
lose part of the state and only unloading the module will clean up
the remaining parts and that's not possible if you have a builtin
driver. If you kill iscsid while having set up an iscsi session
and you cannot unload the driver, you should reboot.


Greetings,
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."