Re: Problem with auto-starup on Debian 6
On Thu, 2013-01-10 at 00:24 -0600, Mike Christie wrote: I think some distros just call iscsi anytime there is a network change like a interface coming up or a interface getting a address. Ubuntu (and I'd guess Debian) does this (well, the on ifup part). It also stops open-iscsi on ifdown. I just had to disable that today. Imagine a virtualization host server. You create a new VM on a new VLAN. You add the relevant bridge interface, bring it up, and *bam*, all your existing, running VMs just lost access to their disks. Likewise, you can't upgrade the open-iscsi package while anything is using iSCSI devices, because it will stop and start the service. I solved these problems by using dpkg-divert on the if-up.d and if-down.d scripts to move them to open-iscsi.disabled and a custom policy-rc.d script to disallow open-iscsi stops or restarts if any VMs are running. Also, at least in my case, it's necessary to restart libvirt-bin after restarting open-iscsi. Are many people really using iSCSI via roaming network connectivity? -- Richard signature.asc Description: This is a digitally signed message part
Re: LU Alias
All `sg_vpd --page=0x83` returns is the IQN: Device Identification VPD page: Addressed logical unit: designator type: NAA, code set: Binary 0x600144f0e431c9004fe3632f0003 Target port: designator type: vendor specific [0x0], code set: ASCII transport: Internet SCSI (iSCSI) vendor specific: iqn.1999-03.com.wiktel:01:krls1 designator type: Target port group, code set: Binary Target port group: 0x0 designator type: Relative target port, code set: Binary Relative target port: 0x2 I'm thinking that OpenIndiana/Illumos/COMSTAR/whatever-component isn't actually exporting this information in any way. -- Richard -- 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 open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: LU Alias
On Thu, 2012-05-10 at 12:21 -0500, Mike Christie wrote: A netapp engineer suggested trying the REPORT IDENTIFYING INFORMATION command. To do this you can use sg_ident from the sg3_utils. $ sudo sg_ident -i 127 /dev/sdm Information type: 0, Maximum information length: 0 bytes Information type: 4, Maximum information length: 256 bytes The only one it could be is 4, since the LU alias field is 255 characters, I think. But here are both: $ sudo sg_ident -i 0 /dev/sdm $ sudo sg_ident -i 4 /dev/sdm bad field in Report identifying information cdb including unsupported service action -- Richard signature.asc Description: This is a digitally signed message part
Re: LU Alias
I'm really referring to the LU alias. I asked about this in #illumos (on freenode). After that discussion, I'm not sure that it's even exposed by the target. Is there an obvious place in the VPD (page 0x80, 0x83, ???) where it should be exported? If so, maybe this is just an issue for the Illumos side. -- Richard signature.asc Description: This is a digitally signed message part
