Mike Christie wrote: > Doron Shoham wrote: >> Hi, >> >> Why does the init script on suse re-discovers all iscsi targets which >> were set >> to automatic login? >> To avoid deadlocks on the root fs there is patch which limits the >> number of retries on first login. >> When doing so, it sets back all the default parameters (overriding any >> user definitions). >> I think it should be like in redhat - just login to all the targets >> which are automatic. >> >> Another issue is that the script logouts only from automatic nodes >> (not from all nodes as in redhat). >> This causes a bug, when iscsi is stopped while manual node is still >> logged-in (session is active). >> The result is that iscsid is down but session is still alive - >> iscsiadm -m session shows this stale session. >> I suggest that we do the same as redhat, any objections? >> >> >> Also, what is the purpose of "node.startup" parameter? >> When is it in use? >> > > node.startup should be renamed record.startup. The possible values are > automatic, manual and onboot. When the init scripts start they can run > over the the db and check which records that the users has requested > autoatmic startup for and login at that time.
For the redhat ones, iscsiadm loops over the records when it does iscsiadm -m node --loginall=automatic > > onboot is used to for the session used for boot/root. It just signals > the tools to handle it differently. During shutdown for example we > cannot kill that session when the init script stop is done, because it > is still needed for root. iscsiadm -m node --logoutall=all does not logout the records marked onboot. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
