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! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]