Re: iSCSI and LVM Volume Groups

2011-08-15 Thread Mike Christie 
On 08/12/2011 11:26 AM, Andrei Bănaru wrote:
 Hello,
 
 To work with KVM on RHEL6 I'm thinking about exporting a LVM Volume Group 
 directly as an iSCSI target LUN. The idea is to export it and then on each 
 server which hosts virtual machines create logical volumes for each virtual 
 machine. I want to achieve scalability and force the users to create the 
 logical volumes on the initiators and not give them access to the storage 
 server. The environment isn't so big so chances that some users create a 
 logical volume at the same time from different initiators can be considered 
 0.
 
 Is there a way to export a LVM VG as an iSCSI target despite the fact that 
 VGs aren't considered block devices ?
 

Are you using scsi-target-utils/tgtd that comes with RHEL 6? If so then
I thought this works. I thought lvm vgs were block devices. Don't they
have a end up having a device mapper device in the kernel? You get some
sort of /dev device and it is a block device right? Maybe I am mixing up
vgs and pgs. In the targets.conf examples there is a lvm example:

#target iqn.2008-09.com.example:server.target1
#backing-store /dev/LVM/somedevice
#/target

But the best place to ask this question is on the target list for your
target. For scsi-target-utils/tgt it would be s...@vger.kernel.org.

This list for the iscsi initiator does not care what you use for the
backing storage. We have no idea what it really is.

-- 
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: open-iscsi issue

2011-08-15 Thread Farhan Ahmed 
Hi Mike,

You mentioned new version is coming on 15th of this month. But it is
not released yet. When do you have plan to release?

Farhan

On Aug 3, 10:43 am, Farhan Ahmed ahmed.far...@gmail.com wrote:
 Thanks Jim and Mike I increased time out from 1 second to 15 second
 and finally array accepted the login request and initiator login. When
 I tried to login from eth5 interface then it times out , anyway I have
 increased timeout from 15 second to 45 second and now all good. Thanks
 a lot. Yes I had already logged case with Equallogic and they are
 still looking into it.

 Last suggestion is should we use multipathing over bonded interface or
 multipathing over simple ethernet interfaces? multipathiong over 2
 bonded interface we are getting same throughput as we are getting
 multipathing over 4 individual interfaces and array has 3 ports so my
 understanding was 3 network interfaces will have more throughput as
 compared to two bonded interface. But bonded interface are good in
 regards of swicth failover or nic module failure , same scnerio which
 I was tryin to test. Even the primary eth2 is down bonded interfcae
 will have no impact.

 What do you guys think about multipath over bonded interface or
 multipathing over interfaces.

 Thanks a lot for for your help guys.

 Farhan

 On Aug 2, 11:21 pm, jim_ram...@dell.com wrote:



  Mike Christie wrote:
   We can see the iscsi login pdu get sent, but we do not see a iscsi 
   response.
   From what I can tell we just seem to see a tcp ack. Then later in packet 
   #104
   we see the initiator give up on waiting for a login response and 
   disconnect
   the tcp/ip connection.

   However, the weird thing is that before we try the normal session login we
   see in packet #10 that a discovery session works ok in this test.

   So command #1 works but command #3 does not and between that time he
   has not done any changes to the iscsi config or network.

  I noticed that after sending the login request (Packet #97) the initiator 
  is closing the connection (Packet #104) after 1 second, which is quite soon 
  - I would suggest adjusting the node.conn[0].timeo.login_timeout value back 
  up to the default of 15 seconds and trying again.

  For more help, I'd recommend contacting the Dell EqualLogic support 
  organization.  They're quite good, and have a lot of experience with Linux 
  (including this tricky multiple-NICS-on-the-same-subnet setup):
     http://support.dell.com/equallogic/

  --
  Jim Ramsay- Hide quoted text -

 - Show quoted text -

-- 
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.