Thank you Nigel for uing my recipe :)
Since my SCSI raid system is now in use I can't make the "truss" tests you
asked me to do. Actually I have a FC raid system to configure, so I made some
testing on it -> a "raw" target as ever.
[b]Target[/b]
...
# iscsitadm list target -v
Target: vp-1252
iSCSI Name:
iqn.1986-03.com.sun:02:b8b3a051-6efe-e561-a2ac-f9370c38003d.vp-1252
Connections: 1
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:000102fa8679.460d01c7
Alias: my.initiator.net
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 010000304829d43600002a0046120d99
VID: SUN
PID: SOLARIS
Type: raw
Size: 698G
Backing store: /dev/rdsk/c0t0d0p0
Status: online
[b]Initiator[/b]
...
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0 <DEFAULT cyl 9726 alt 2 hd 255 sec 63>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
1. c1t4d0 <VP-1252--FB951293-VOL#00-R001-698.49GB>
/iscsi/[EMAIL PROTECTED],0
Specify disk (enter its number): ^D
# zpool create -m /export/vp-1252 vp-1252 c1t4d0
<!-- Delay -->
^C
<!-- Delay -->
# zpool list
no pools available
[b]Debug outputs on the target[/b]
# tail /var/svc/log/system-iscsitgt\:default.log
[ Apr 2 10:29:25 Stopping because process dumped core. ]
[ Apr 2 10:29:25 Executing stop method ("/lib/svc/method/svc-iscsitgt stop
83") ]
[ Apr 2 10:29:25 Method "stop" exited with status 0 ]
[ Apr 2 10:29:25 Executing start method ("/lib/svc/method/svc-iscsitgt start")
]
[ Apr 2 10:29:25 Method "start" exited with status 0 ]
[ Apr 2 10:29:32 Stopping because process dumped core. ]
[ Apr 2 10:29:32 Executing stop method ("/lib/svc/method/svc-iscsitgt stop
85") ]
[ Apr 2 10:29:32 Method "stop" exited with status 0 ]
[ Apr 2 10:29:32 Executing start method ("/lib/svc/method/svc-iscsitgt start")
]
[ Apr 2 10:29:32 Method "start" exited with status 0 ]
# cd /var/crash/my.target.net
# ls -l
total 160912
-rw------- 1 root root 5911035 Apr 2 10:28 core.iscsitgtd.366
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.394
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.403
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.411
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.419
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.427
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.435
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.443
-rw------- 1 root root 5868119 Apr 2 10:28 core.iscsitgtd.451
-rw------- 1 root root 5868119 Apr 2 10:29 core.iscsitgtd.459
-rw------- 1 root root 5868119 Apr 2 10:29 core.iscsitgtd.467
-rw------- 1 root root 5868119 Apr 2 10:29 core.iscsitgtd.475
-rw------- 1 root root 5868119 Apr 2 10:29 core.iscsitgtd.483
-rw------- 1 root root 5868119 Apr 2 10:29 core.iscsitgtd.491
# mdb core.iscsitgtd.491
Loading modules: [ libavl.so.1 libc.so.1 libnvpair.so.1 libuutil.so.1 ld.so.1 ]
> $c
libc.so.1`_lwp_kill+0x15(9, 6)
libc.so.1`raise+0x22(6)
libc.so.1`abort+0xcd(8091cb0, 8091d80, 65737341, 6f697472, 6166206e, 64656c69)
libc.so.1`_assert+0x6e(8075568, 8075558, 265)
t10_cmd_state_machine+0xcb(8091d80, 3)
trans_aioread+0x4c(8091d80, 809b550, 2000, 16400, 0, 8094268)
raw_read+0x4a7(8091d80, 808fb98, 10)
raw_cmd+0x23(8091d80, 808fb98, 10)
lu_runner+0x79b(8091e00)
libc.so.1`_thr_setup+0x52(cdf51800)
libc.so.1`_lwp_start(cdf51800, 0, 0, 0, 0, 0)
>
As you see, we get the same kind of error.. I was hoping it to work because of
the "parity error" output I got when I made that test on a SCSI disk, since I
have not been able to make the test with "parity check" disabled on the SCSI
controleur.
Thanks to all for the support,
Rafael Navaza.
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
