** Changed in: open-iscsi (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123192
Title:
open-iscsi removes modules on stop but shoul
Just to document an IRC conversation, another more obvious instance of
the problem is:
a) use OCFS2 with a shared heartbeat service on an iSCSI connected SAN - assume
this is not in the configuration file for iSCSI (not that it makes much
difference)
b) OCFS2 will access the raw block device wit
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => High
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubun
Actually one problem we are seeing should be pretty universal.
When using OCFS2, it will open the shared iSCSI device with O_DIRECT,
and write a heartbeat there. If this errors, then the node self fences
(i.e. reboots).
If the open-iscsi package is upgraded, it calls the init with a stop
method,
Ritesh,
We're actually seeing 2 problems:
1. on an upgrade to the open-iscsi module, between the stop and the
subsequent start, a daemon is calling iscsiadm and that is failing as
the module isn't loaded. Arguably this is our problem.
2. on a separate system, we have something which does somethi
