Re: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-04-18 Thread Andrew Moise

On Mon, Apr 14, 2008 at 3:38 PM, Andrew Moise <[EMAIL PROTECTED]> wrote:
>   Debian kernel guys, how do you feel about the situation?  Would you
>  be willing to apply a patch upgrading 2.6.24's iscsi subsystem to the
>  version from 2.6.25 if that fixed serious known bugs?  Would you
>  prefer for a backported fix to be applied to the stable series and
>  then get the fix from there?  How do you feel in general?

  As it turns out, I'm wholly mistaken.  Debian is planning to use
2.6.25 or higher for the next stable release, so this will be a
non-issue.  Hooray!

http://lists.debian.org/debian-kernel/2008/03/msg00531.html

  Thanks.

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-04-14 Thread Andrew Moise

On Mon, Apr 14, 2008 at 12:56 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>  You mean you want the sync cache fix right? Can I just send a patch for
>  what went into 2.6.25 since there are several fixes in there you guys
>  probably want and because the patch will be easier for me to make? :)
>  Just doing a patch for the cache sync will be difficult because it was
>  made on top of other patches.

  Hm... I can't speak for the kernel maintainers, but the smaller the
patch is the more likely it will be to get accepted I would imagine.
Perhaps I should wait until hearing word from them before asking you
to prepare particular patches.
  Debian kernel guys, how do you feel about the situation?  Would you
be willing to apply a patch upgrading 2.6.24's iscsi subsystem to the
version from 2.6.25 if that fixed serious known bugs?  Would you
prefer for a backported fix to be applied to the stable series and
then get the fix from there?  How do you feel in general?
  Thanks.

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-04-14 Thread Mike Christie

Andrew Moise wrote:
> On Thu, Feb 28, 2008 at 10:00 AM, Mike Christie <[EMAIL PROTECTED]> wrote:
>>  Andrew Moise wrote:
>>  >   Are there any iscsi fixes in 2.6.24, or is it 2.6.25 or nothing?
>>
>>  There are major fixes in 2.6.23 for error handler races and an oops.
>>  There is one major fix in 2.6.24 for a write out race.
>>
>>  If you guys tell me what kernel you are using, I can try to port the
>>  upstream patches to your kernel for you guys.
> 
>   Okay, it looks to me like it's settled that Debian is going to use
> 2.6.24 for the next stable release (currently it's based on 2.6.24.4).
>  If you can point me to a patch which fixes the write out race, I can
> apply it to Debian's kernel and give it some testing (and also talk to
> the Debian kernel maintainers to try to get it included).
>   Cheers!
> 

You mean you want the sync cache fix right? Can I just send a patch for 
what went into 2.6.25 since there are several fixes in there you guys 
probably want and because the patch will be easier for me to make? :) 
Just doing a patch for the cache sync will be difficult because it was 
made on top of other patches.


--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-04-13 Thread Andrew Moise

On Thu, Feb 28, 2008 at 10:00 AM, Mike Christie <[EMAIL PROTECTED]> wrote:
>  Andrew Moise wrote:
>  >   Are there any iscsi fixes in 2.6.24, or is it 2.6.25 or nothing?
>
>  There are major fixes in 2.6.23 for error handler races and an oops.
>  There is one major fix in 2.6.24 for a write out race.
>
>  If you guys tell me what kernel you are using, I can try to port the
>  upstream patches to your kernel for you guys.

  Okay, it looks to me like it's settled that Debian is going to use
2.6.24 for the next stable release (currently it's based on 2.6.24.4).
 If you can point me to a patch which fixes the write out race, I can
apply it to Debian's kernel and give it some testing (and also talk to
the Debian kernel maintainers to try to get it included).
  Cheers!

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-02-23 Thread Andrew Moise

On 2/22/08, Andrew Moise <[EMAIL PROTECTED]> wrote:
>  In any case, I'll try the new userspace tools with 2.6.25-rc2 over
> the weekend and let you know.  If it seems to work out okay (and I
> have a ton of time to kill :-), I'll also try the new kernel modules
> on the 2.6.18 kernel that I was using previous to this whole endeavor.

  Okay, the userspace tools in open-iscsi 2.0.868-rc1, when combined
with either the 2.6.25-rc2 kernel or the Debian 4.0 kernel (2.6.18)
with the backported driver, seem not to have this problem.  They also
each survived several hours of bonnie++, so I'll plan to gingerly put
2.6.18 with the backported driver into production this week and see
how it does.
  Thanks very much for providing the backported drivers; they make
things a lot easier for me :-).
  Cheers.

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-02-22 Thread Andrew Moise

On 2/22/08, Mike Christie <[EMAIL PROTECTED]> wrote:
> Andrew Moise wrote:
> >   If I still see the problem with the management interface in a newer
> > kernel, I'll file a separate bug report about it.
>
> Ok thanks for the info. I do not think open-iscsi will be able to do
> anything about that. The scsi layer does the scanning and it creates the
> devices, so we have no control. cc linux-scsi on the bug report if you
> make one.

  Okay, will do.

> It is no problem. It says not stable on the web page, for a good reason
> :)

  Heh.  When you say it's "not stable," do you mean that there's still
a lot of active development happening, or do you mean that the code
may still be somewhat unreliable?  Or both?  :-)

> There are just too many combos and I cannot back port to every distro
> kernel, so we try to distribute kernel modules in the open-iscsi.org
> which can work with older kernels. It is a pain for distros to
> integrate, so I am not sure what else to do. For Red Hat I have to
> actually back port the code, and one distro is all I can take :)
>
> You need the new userspace tools for all the combos.
>
> - You can use the new userspace tools and kernel modules on
> open-iscsi.org with 2.6.16 - 2.6.24.
>
> - You can use the new userspace tools with 2.6.25-rc2 and above.

  Hm... so is each version of the userspace tools intended to work
only with the kernel modules included in the same tarball on
open-iscsi.org?  Or is it just that in this particular case, there are
necessary bug fixes in both the new userspace tools and the new kernel
modules?
  Sorry if I'm asking basic questions about the relationship between
the userspace tools, the modules in the open-iscsi.org tarballs, and
the modules in the stock kernels.  I'm still a little unclear on how
it all fits together, though.
  In any case, I'll try the new userspace tools with 2.6.25-rc2 over
the weekend and let you know.  If it seems to work out okay (and I
have a ton of time to kill :-), I'll also try the new kernel modules
on the 2.6.18 kernel that I was using previous to this whole endeavor.
  Thanks!

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-02-22 Thread Mike Christie

Andrew Moise wrote:
> On 2/22/08, Mike Christie <[EMAIL PROTECTED]> wrote:
>> What other issues are you hitting. They might be fixed in the new
>>  release or we might still need a bug report. Let me know.
> 
>   The etch kernel I was originally using (2.6.18) crashed the machine
> when I tried to log in to the MD3000i enclosure, 2.6.22 hung on logout
> as I mentioned, the inband management interface was detected as a
> separate disk by open-iscsi (which caused I/O errors when the kernel
> tried to read a partition table from it and couldn't), and one person
> on a Dell mailing list mentioned kernel panics in 2.6.22 in addition
> to the hang on logout.
>   If I still see the problem with the management interface in a newer
> kernel, I'll file a separate bug report about it.  Of course, it might
> just be ridiculous behavior on the part of the hardware that the
> driver is expected to "know" how to handle properly in order to
> represent as a management interface.  It's also easily worked around
> on my end by configuring the enclosure not to present an inband
> management interface.


Ok thanks for the info. I do not think open-iscsi will be able to do 
anything about that. The scsi layer does the scanning and it creates the 
devices, so we have no control. cc linux-scsi on the bug report if you 
make one.


> 
>> This one was the fault of the upstream kernel changing behavior on us,
>>  and not iscsi.
> 
>   Makes sense.  I didn't mean to sound critical of open-iscsi; I was
> just wondering what the intended status of the code was.

It is no problem. It says not stable on the web page, for a good reason 
:) There are just too many combos and I cannot back port to every distro 
kernel, so we try to distribute kernel modules in the open-iscsi.org 
which can work with older kernels. It is a pain for distros to 
integrate, so I am not sure what else to do. For Red Hat I have to 
actually back port the code, and one distro is all I can take :)

> 
>>  It is fixed in 2.6.25-rc2, and the kernel modules in the current rc
>>  release:
>>  http://www.open-iscsi.org/bits/open-iscsi-2.0-868-rc1.tar.gz
> 
>   Okay, I'll try to test that kernel this weekend and let you know how
> it works for me.  Thanks!
>   Just to check: Are you saying that I need a 2.6.25-rc2 kernel _and_
> the 2.0-868-rc1 userspace tools, or are you saying that I either need
> a 2.6.25-rc2 kernel _or_ the new kernel module, which is included with
> the 2.0-868-rc1 userspace tools?
> 

Sorry for the confusion.

You need the new userspace tools for all the combos.

- You can use the new userspace tools and kernel modules on 
open-iscsi.org with 2.6.16 - 2.6.24.

- You can use the new userspace tools with 2.6.25-rc2 and above.

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-02-22 Thread Andrew Moise

On 2/22/08, Mike Christie <[EMAIL PROTECTED]> wrote:
> What other issues are you hitting. They might be fixed in the new
>  release or we might still need a bug report. Let me know.

  The etch kernel I was originally using (2.6.18) crashed the machine
when I tried to log in to the MD3000i enclosure, 2.6.22 hung on logout
as I mentioned, the inband management interface was detected as a
separate disk by open-iscsi (which caused I/O errors when the kernel
tried to read a partition table from it and couldn't), and one person
on a Dell mailing list mentioned kernel panics in 2.6.22 in addition
to the hang on logout.
  If I still see the problem with the management interface in a newer
kernel, I'll file a separate bug report about it.  Of course, it might
just be ridiculous behavior on the part of the hardware that the
driver is expected to "know" how to handle properly in order to
represent as a management interface.  It's also easily worked around
on my end by configuring the enclosure not to present an inband
management interface.

> This one was the fault of the upstream kernel changing behavior on us,
>  and not iscsi.

  Makes sense.  I didn't mean to sound critical of open-iscsi; I was
just wondering what the intended status of the code was.

>  It is fixed in 2.6.25-rc2, and the kernel modules in the current rc
>  release:
>  http://www.open-iscsi.org/bits/open-iscsi-2.0-868-rc1.tar.gz

  Okay, I'll try to test that kernel this weekend and let you know how
it works for me.  Thanks!
  Just to check: Are you saying that I need a 2.6.25-rc2 kernel _and_
the 2.0-868-rc1 userspace tools, or are you saying that I either need
a 2.6.25-rc2 kernel _or_ the new kernel module, which is included with
the 2.0-868-rc1 userspace tools?

>  To work around the problem you have to disable write caching on the
>  target (not all targets can do this though).

  Unfortunately I don't see a way to do this with my target :-(.
  Thanks!

--~--~-~--~~~---~--~~
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: open-iscsi: Hangs trying to log out of Dell MD3000i

2008-02-22 Thread Mike Christie

Andrew Moise wrote:
> forwarded 466954 open-iscsi@googlegroups.com
> thanks
> 
>   Hi all.
>   I'm having a bit of trouble with open-iscsi on kernel 2.6.22.18 from
> Debian backports; I seem to be able to log in to my storage array, but
> when I log out, iscsiadm (and later modprobe) seem to hang forever.
> I've filed a Debian bug report about this at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466954, and attached
> a bug report in Linux kernel bug report format (since it's quite
> large, I didn't paste it inline).  This is a production system, but
> I've got some ability to muck with it on weekends and such, so I can
> try more recent vanilla/git kernels if that will help with the
> debugging.
>   It seems that the iSCSI system in the kernels I've been trying is
> not very mature; I note that http://www.open-iscsi.org/ says, "Stable

What other issues are you hitting. They might be fixed in the new 
release or we might still need a bug report. Let me know.

> releases: not available yet."  I had been planning to put this into
> production -- is iSCSI in a state such that that's a reasonable goal,
> or should I just be planning to return this hardware and/or find an
> alternative way of interfacing with it?
>   Thanks.

This one was the fault of the upstream kernel changing behavior on us, 
and not iscsi.

It is fixed in 2.6.25-rc2, and the kernel modules in the current rc 
release:
http://www.open-iscsi.org/bits/open-iscsi-2.0-868-rc1.tar.gz

To work around the problem you have to disable write caching on the 
target (not all targets can do this though).

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