Rick, I'm trying to comply with your request to retry the test without
specifying the '--type raw', but I'm struggling to get the correct syntax.

If I simply remove  '--type raw', and leave the rest of the line as it is,
then I get an error:

# iscsitadm create target --backing-store /dev/dsk/c0t0d0p0 --lun 0 zd-4565
iscsitadm: Error Failed to create backing store

So I guess the pathname is no longer valid with out the '--type raw'.
I had a look at the iscsitadm man page, and it does not give many examples.
I must admit I am not very familiar with specifying storage device names
for Solaris.  In this case I just have a single scsi drive hanging off a adaptec
pci card, and I want to totally dedicate it to being the storage device for
the iscsi target. So please could you offer some advise on the correct
pathname &/or syntax to use for this scenario.

On a wider note, I guess the question is this - "For what Rafael is trying to 
do,
is using  '--type raw' the right approach. Rick, you seem to be saying - NO".

Also, 'rlhamil' poses an interesting question, regarding using the iscsi target
to share a dvd burner.  I guess he is thinking of something like the
'Alcohol 120%' software available for Windows:
http://support.alcohol-soft.com/knowledgebase.php?postid=20309

By the way, I did try using 'truss', to look at what iscsitgt was doing before
the assertion.  The following is edited highlights of the calls:

/[EMAIL PROTECTED]:   -> raw_cmd(0x4b2e80, 0x472050, 0x10, 0x0, 0x481550, 
0x48ec40)
/[EMAIL PROTECTED]:     -> raw_read(0x4b2e80, 0x472050, 0x10, 0x0, 0x500, 
0x446490)
/[EMAIL PROTECTED]:       -> trans_params_area(0x4b2e80, 0x472050, 0x10, 0x0, 
0x500, 0x446490)
/[EMAIL PROTECTED]:       <- trans_params_area() = 0x472890
/[EMAIL PROTECTED]:       -> trans_cmd_dup(0x4b2e80, 0x0, 0x0, 0x0, 0x0, 0xe000)
/[EMAIL PROTECTED]:       <- trans_cmd_dup() = 0x4a1ab0
/[EMAIL PROTECTED]:       -> trans_aioread(0x4a1ab0, 0x474010, 0x2000, 0x0, 
0x480d50, 0x490f78)
/[EMAIL PROTECTED]:       <- trans_aioread() = 0
/[EMAIL PROTECTED]:       -> trans_aioread(0x4b2e80, 0x476410, 0x2000, 0x2000, 
0x480cd0, 0x490f88)
/[EMAIL PROTECTED]:       <- trans_aioread() = 0
/[EMAIL PROTECTED]:       -> trans_aioread(0x4b2e80, 0x4a7410, 0x2000, 0x4000, 
0x480ad0, 0x46b368)
/16:    write(2, " A s s e r t i o n   f a".., 49)      Err#89 ENOSYS

Rick, can you give some further information on the 'bug' you spotted, for the
benefit of those of us that like to look at your code, and aspire to understand
what it is doing.
Thanks
Nigel Smith
 
 
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to