Re: open-iscsi and discover newly created LUN
what are the steps for installing ISCSI on Ubuntu 9.4? I am having a horrible time doin just that I would love to recover or even see the luns I have provisioned Paul Cooper Konrad Rzeszutek wrote: On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. You get that in dmesg? Or is that something the aray can do, but you have to configure it? A rescan may not be necessary if this information is received by the open-iscsi. Huh? Why not? I mean if the LUN changed (it changed size for example), don't you want to rescan the LUN to pick up the changes? Thought where this is handled is bit complex. You can either handle it in the kernel (and have to deal with re-syncing all of the structures related to the block disk), or run a user-land program that deletes the old block disks and re-creates it (by kicking of a REPORT_LUN scan). --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: open-iscsi and discover newly created LUN
On 06/15/2009 12:41 AM, shyam_i...@dell.com wrote: -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Saturday, June 13, 2009 8:30 AM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On 06/12/2009 01:16 AM, TheR wrote: Using open-iscsi as initiator on ubuntu 9.04. I want to set up virtual environment with iscsi target server which is ubuntu based. On target decided to use single tid under which I create multple LUN-s, which represent disks used by initiator which is KVM server. One LUN becomes a disk used by one virtual machine on KVM server. My problem is when I create new LUN on target (under same tid), this LUN doesn't get recognized by initiator without restarting initiator iscsi service. Which in return breaks all curently running machines on KVM server. I have seen same behaviour on Red Hat 5.1. On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. A rescan may not be necessary if this information is received by the open-iscsi. Do you have a background on the SCSI-ML part ? If the unit attention comes in a iscsi async pdu, then we handle it today in iscsid by kicking off a rescan which adds new devices. It does not delete stale ones, because the scsi-ml sysfs scan interface does not do this. If the unit attention comes with scsi command sense like normal, people have been working on it like here: http://marc.info/?l=linux-scsim=123852561314129w=2 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: open-iscsi and discover newly created LUN
-Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Konrad Rzeszutek Sent: Monday, June 15, 2009 8:39 PM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. You get that in dmesg? Or is that something the aray can do, but you have to configure it? It is usually programmed into the array firmware. A rescan may not be necessary if this information is received by the open-iscsi. Huh? Why not? I mean if the LUN changed (it changed size for example), don't you want to rescan the LUN to pick up the changes? Not anymore.. Rescanning is a parallel scsi thingie ..see http://www.t10.org/ftp/t10/document.06/06-411r0.pdf --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: open-iscsi and discover newly created LUN
-Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Monday, June 15, 2009 9:15 PM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On 06/15/2009 12:41 AM, shyam_i...@dell.com wrote: -Original Message- From: open-iscsi@googlegroups.com [mailto:open- is...@googlegroups.com] On Behalf Of Mike Christie Sent: Saturday, June 13, 2009 8:30 AM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On 06/12/2009 01:16 AM, TheR wrote: Using open-iscsi as initiator on ubuntu 9.04. I want to set up virtual environment with iscsi target server which is ubuntu based. On target decided to use single tid under which I create multple LUN-s, which represent disks used by initiator which is KVM server. One LUN becomes a disk used by one virtual machine on KVM server. My problem is when I create new LUN on target (under same tid), this LUN doesn't get recognized by initiator without restarting initiator iscsi service. Which in return breaks all curently running machines on KVM server. I have seen same behaviour on Red Hat 5.1. On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. A rescan may not be necessary if this information is received by the open-iscsi. Do you have a background on the SCSI-ML part ? If the unit attention comes in a iscsi async pdu, then we handle it today in iscsid by kicking off a rescan which adds new devices. It does not delete stale ones, because the scsi-ml sysfs scan interface does not do this. If the unit attention comes with scsi command sense like normal, people have been working on it like here: http://marc.info/?l=linux-scsim=123852561314129w=2 Ah Ok. Thanks for the link. I guess this is still WIP. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: open-iscsi and discover newly created LUN
On Mon, Jun 15, 2009 at 10:48:49PM +0530, shyam_i...@dell.com wrote: -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Konrad Rzeszutek Sent: Monday, June 15, 2009 8:39 PM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. You get that in dmesg? Or is that something the aray can do, but you have to configure it? It is usually programmed into the array firmware. A rescan may not be necessary if this information is received by the open-iscsi. Huh? Why not? I mean if the LUN changed (it changed size for example), don't you want to rescan the LUN to pick up the changes? Not anymore.. Rescanning is a parallel scsi thingie ..see http://www.t10.org/ftp/t10/document.06/06-411r0.pdf I think the majority of storages that are in usage right now (at least for the SMB market) don't employ this standard. Hence to support those storage, you would still need to do the old way (ie, find out what changed, do an SCSI INQ see if the Peripheral Qualifier changed, or if device type has changed from 1fh to 00h, etc). --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: open-iscsi and discover newly created LUN
-Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Saturday, June 13, 2009 8:30 AM To: open-iscsi@googlegroups.com Subject: Re: open-iscsi and discover newly created LUN On 06/12/2009 01:16 AM, TheR wrote: Using open-iscsi as initiator on ubuntu 9.04. I want to set up virtual environment with iscsi target server which is ubuntu based. On target decided to use single tid under which I create multple LUN-s, which represent disks used by initiator which is KVM server. One LUN becomes a disk used by one virtual machine on KVM server. My problem is when I create new LUN on target (under same tid), this LUN doesn't get recognized by initiator without restarting initiator iscsi service. Which in return breaks all curently running machines on KVM server. I have seen same behaviour on Red Hat 5.1. On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan Mike - The target can initiates a UNIT ATTENTION with additional sense as Report LUN data changed, I don't see that currently being handled by the SCSI-ML. A rescan may not be necessary if this information is received by the open-iscsi. Do you have a background on the SCSI-ML part ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
open-iscsi and discover newly created LUN
Using open-iscsi as initiator on ubuntu 9.04. I want to set up virtual environment with iscsi target server which is ubuntu based. On target decided to use single tid under which I create multple LUN-s, which represent disks used by initiator which is KVM server. One LUN becomes a disk used by one virtual machine on KVM server. My problem is when I create new LUN on target (under same tid), this LUN doesn't get recognized by initiator without restarting initiator iscsi service. Which in return breaks all curently running machines on KVM server. I have seen same behaviour on Red Hat 5.1. What is the common practice in this kind of environment. Do you create new tid on target for every new disk? by TheR --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: open-iscsi and discover newly created LUN
On 06/12/2009 01:16 AM, TheR wrote: Using open-iscsi as initiator on ubuntu 9.04. I want to set up virtual environment with iscsi target server which is ubuntu based. On target decided to use single tid under which I create multple LUN-s, which represent disks used by initiator which is KVM server. One LUN becomes a disk used by one virtual machine on KVM server. My problem is when I create new LUN on target (under same tid), this LUN doesn't get recognized by initiator without restarting initiator iscsi service. Which in return breaks all curently running machines on KVM server. I have seen same behaviour on Red Hat 5.1. On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what version is in there), you can do iscsiadm -m session -r $SID --rescan (SID is in iscsiadm -m session -P 3) or iscsiadm -m node -T target --rescan or iscsiadm -m node --rescan iscsiadm -m session --rescan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
