Re: Accessing specific lun in target with open-e
Hello Mike, Mike Christie wrote: Fred Blaise wrote: Hi, Mike Christie wrote: Fred Blaise wrote: Hello all, I am using open-e DSS storage (http://open-e.com). I usually have 1 lun per target, but for backup purposes, I take snapshots for each lun. This snapshot then becomes a part of the parent LUN target, so that TargetX has LunA and LunS (snapshot). When I login to the target, however, I see only one LUN. I have a udev rule that create a symlink as /dev/iscsi_XX-. I see the main lun of the target, but not the snapshot. After resetting the open-e iscsi connections (sort of IETd implementation), and rescanning the target on my initiator, a P 3 listing says this: Are you rescanning the target with iscsiadm or by hand? With iscsiadm, such as iscsiadm -m node -R -T target_name_here The iscsi layer does not do the actaully scanning. The scsi layer does this and adds devices. You should enable the scsi logging for the scsi layer and send that output. I do not remember the exact values to use. You should search on google for this. There is a nice tool to make it easier too. You could also do a wireshark trace from the initiator. Fire wireshark up, then run the iscsiadm command, and then send the trace here. That won't be necessary. I opened up a ticket to open-e, and in fact, the snapshot, while being in use, was not activated. It works better now. Thank you. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Accessing specific lun in target with open-e
Hello all, I am using open-e DSS storage (http://open-e.com). I usually have 1 lun per target, but for backup purposes, I take snapshots for each lun. This snapshot then becomes a part of the parent LUN target, so that TargetX has LunA and LunS (snapshot). When I login to the target, however, I see only one LUN. I have a udev rule that create a symlink as /dev/iscsi_XX-. I see the main lun of the target, but not the snapshot. After resetting the open-e iscsi connections (sort of IETd implementation), and rescanning the target on my initiator, a P 3 listing says this: Target: iqn.2008-02:open-e-1.rt Current Portal: 172.17.77.12:3260,1 Persistent Portal: 172.17.77.12:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface IPaddress: 172.17.77.51 Iface HWaddress: default Iface Netdev: default SID: 261 iSCSI Connection State: LOGGED IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 8192 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 262State: running scsi262 Channel 00 Id 0 Lun: 3 Attached scsi disk sds State: running Nothing said about the snapshot. Anyone has an idea? Would that be a specific to open-e dss storage? Thank you for any suggestions. fred --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Accessing specific lun in target with open-e
Attached scsi disk sds State: running Nothing said about the snapshot. Anyone has an idea? Would that be a specific to open-e dss storage? What does #sg_luns /dev/sds give you? (sg_luns is part of sg3_utils package). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Accessing specific lun in target with open-e
Fred Blaise wrote: Hello all, I am using open-e DSS storage (http://open-e.com). I usually have 1 lun per target, but for backup purposes, I take snapshots for each lun. This snapshot then becomes a part of the parent LUN target, so that TargetX has LunA and LunS (snapshot). When I login to the target, however, I see only one LUN. I have a udev rule that create a symlink as /dev/iscsi_XX-. I see the main lun of the target, but not the snapshot. After resetting the open-e iscsi connections (sort of IETd implementation), and rescanning the target on my initiator, a P 3 listing says this: Are you rescanning the target with iscsiadm or by hand? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
