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, then the start method. There may be a gap between these two if lots of packages are being upgraded. It's actually not just the modprobes that are the problem here, it's the fact that it logs out of all iscsi targets WHETHER OR NOT THEY ARE IN THE CONFIG FILE which is the issue. In one scenario here we aren't using the config file at all - we're calling iscsiadm or equivalent to mount the LUNs directly. What should be happening here I think is it shutting down the daemon and arguably stopping the targets it started on boot. I don't see why it's interfering with other targets it had nothing to do with starting. Or at least there should be some /etc/default type setting that says 'please don't interfere with running targets'. What happens if your root directory is on iscsi? (serious question - I'm interested in how it's meant to cope) -- 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 should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1123192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
