>> devfsadm -i iscsi # to create the device on sf3
>> iscsiadm list target -Sv| egrep 'OS Device|Peer|Alias' # not empty
>> Alias: vol-1
>> IP address (Peer): 10.194.67.111:3260
>> OS Device Name:
>> /dev/rdsk/c1t0100004005A267C100002A0045E2F524d0s2
this is where my confusion began.
I don't know what is the device c1t0....4d0s2 for ? I mean what does it
represents?
I've found that the ``OS Device Name'' (c1t0....4d0s2) is created after
the invocation:
devfsadm -i iscsi # to create the device on sf3
but no way, this is not a device that you can use.
you can find the device only with the command:
format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <IC35L120AVV207-0 cyl 59129 alt 2 hd 16 sec 255>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
1. c0t2d0 <IC35L120- VNC602A6G9E2T-0001-115.04GB>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
2. c1t0100004005A267C100002A0045E308D2d0 <SUN-SOLARIS-1-6.68GB>
/scsi_vhci/[EMAIL PROTECTED]
and then if you create the zpool with:
zpool create tank c1t0100004005A267C100002A0045E308D2d0
it works !!
BUT.. BUT... and re-BUT
Since this, and with all this virtualization... how can I link a device
name on my iscsi's client with the device name on my iscsi'server.
Because, Imagine that you are in my situation where I want to have
(let's say) 4 iscsi'server with at maximum 16 disks attached by
iscsi'server. And that you have at least 2 iscsi's client which will
consolidate this space with zfs. And suddenly, you can see with zpool
that a disk is dead. So I have to be able to replace this disk and so
for this, I have to know on which one of the 4 machine it resides and
which disk it is.
so does some of you knows a little bit about this ?
Ced.
--
Cedric BRINER
Geneva - Switzerland
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
