This is a tough call, since ocfs2 can also be used on FC hardware, which doesn't need a network connection to share storage. However, given that ocfs2 requires the network to do the clustered locking and communication via o2cb, it makes sense to put its init scripts into runlevel 2, IMO.
-- ocfs2 startup link prior to open-iscsi https://bugs.launchpad.net/bugs/246613 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in ubuntu. Status in “ocfs2-tools” source package in Ubuntu: New Bug description: Binary package hint: ocfs2-tools The ocfs2-tools package creates a startup link at /etc/rcS.d/S65ocfs2. However, the ocfs2 filesystem is (as I understand it) intended for use as a network shared file system. A common way to accomplish this is through the use of iSCSI. The startup link for open-iscsi is created at /etc/rc2.d/S20open-iscsi which means that when ocfs2 starts the iSCSI layer is not yet in place and thus the volume(s) are not mounted. Moving the ocfs2 startup link to /etc/rc2.d corrects the issue. I'm not sure if the link for ocfs2 or open-iscsi should be the one to move. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
