Open iscsi causes machine to hang on reboot
Andreas Bergstrøm
handle several Promise VTrak m500i arrays. The problem I have is that
when I install open iscsi, the machine hangs on reboot.
I have tried shutdown -h 0 as described here: http://groups.google.com/group/open-iscsi/browse_thread/thread/cc10498655b40507/f36cc00ba6cc0657?lnk=gst&q=hangs+on+reboot#f36cc00ba6cc0657
As well as the reboot= flags given to the kernel described here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/115906
Logs and other system information is available here: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/181188
I have also played around with the acpi= flags to the kernel at boot,
but have been unable to find a resolution allowing the machine not to
hang when rebooting. (I even tried uninstalling open-iscsi, which
caused the machine to be able to fully reboot again.)
Any tips/fixes/advice on what to do next would be very welcome.
Regards,
--
Andreas Bergstrøm
Østfold University College
Dept. of Computer Sciences
http://media.hiof.no/
Mike Christie
> I am setting up a new server with Ubuntu Server 7.10 and open iscsi to
> handle several Promise VTrak m500i arrays. The problem I have is that
> when I install open iscsi, the machine hangs on reboot.
>
> I have tried shutdown -h 0 as described here: http://groups.google.com/group/open-iscsi/browse_thread/thread/cc10498655b40507/f36cc00ba6cc0657?lnk=gst&q=hangs+on+reboot#f36cc00ba6cc0657
>
I am not sure if that will work for you because I am not sure what the
ubuntu scripts do. The shutdown -h workaround is for a RHEL/Fedora
scripts issue.
What are the last messages printed out when you reboot the box? Is it
something about sending a cache sync for sdXYZ, then a message about a
conn error? If so then the ubuntu scripts are probably turning off the
network too soon. They need to log off all the sessions then stop the
network, or modify the shutdown sciprts so they do not shutdown the
network if iscsi is running.
Andreas Bergstrøm
On 8. jan.. 2008, at 10:29, Mike Christie wrote:
> I am not sure if that will work for you because I am not sure what the
> ubuntu scripts do. The shutdown -h workaround is for a RHEL/Fedora
> scripts issue.
>
> What are the last messages printed out when you reboot the box? Is it
> something about sending a cache sync for sdXYZ, then a message about a
> conn error? If so then the ubuntu scripts are probably turning off the
> network too soon. They need to log off all the sessions then stop the
> network, or modify the shutdown sciprts so they do not shutdown the
> network if iscsi is running.
No, there is no cache sync error messages, nor conn error messages.
I have tried rebooting after having unmounted and then stopping the
open-iscsi service manually, but it still hung on reboot.
Usually it gives an
iscsi: can not broadcast skb (-3)
after the rebooting now message, but that came earlier when I stopped
iscsi manually, and appeared unrelated to me.
However, the /dev/sdx devices created by open-iscsi continues to exist
after iscsi targets are logged off and disconnected. Could this be the
cause of the issue?
Regards
--
Andreas Bergstrøm
http://blog.andreasb.net
Mike Christie
Yeah, the iscsi stuff is not getting shutdown completely. There is a bug
when using 2.6.21 and newer with targets that are using write back cache
like your target.
There is a fix for the upstream 2.6.25 kernel when it comes out. And in
the open-iscsi git tree there is a fix in the kernel modules we
distribute in that tarball.
Mike Christie
Try this tarball which is a rollup of what is in git and what I am
trying to finish up for the next release:
http://open-iscsi.org/bits/open-iscsi-2.0-868-test1.tar.gz
You have to use the kernel modules and tools from this tarball. Do not
use the tools or iscsi modules from Ubuntu.
Andreas Bergstrøm
On 8. jan.. 2008, at 11:01, Mike Christie wrote:
>
> Mike Christie wrote:
> Try this tarball which is a rollup of what is in git and what I am
> trying to finish up for the next release:
> http://open-iscsi.org/bits/open-iscsi-2.0-868-test1.tar.gz
>
> You have to use the kernel modules and tools from this tarball. Do not
> use the tools or iscsi modules from Ubuntu.
I am happy to report that after a download, make and make install the
machine is now able to reboot properly. :)
Wilton
problem so I'll state the resolution here for posterity.
My problem was that the shutdown scripts didn't seem to be ordered
properly. The network was getting shut down before iscsi had a chance
to clear the cache, so the iscsi daemon was hanging. I reordered the
scripts and it started working. I know this isn't recommended, but it
worked for me.
On Jan 8, 3:21 am, Andreas Bergstrøm <andreas.bergst...@hiof.no>
wrote: