[Expired for ocfs2-tools (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in
Should be, but you could also make sure by:
update-rc.d -f o2cb remove
update-rc.d o2cb disable
The only thing that I can imagine atm is that for some reason when
creating the cluster it caught the o2cb one instead of the cman one. You
should make sure ocfs_controld.cman is running as well as
No having used cman with OCFS2 before, and assuming that the o2cb init
script initializes the cluster o2cb instead of cman, shouldn't you be
disabling disabling it? (Please correct me if I'm wrong)
Cheers,
Marking this bug report as incomplete!
** Changed in: ocfs2-tools (Ubuntu)
Status:
i have disabled o2cb as i said above.
the cofiguration for o2cb is: /etc/default/o2cb
the directive is set:
O2CB_ENABLED=false
hence it is disabled. no?
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to
no o2cb service is not enabled, start o2cb is set to false, i do not
want ocfs2 to utilize the o2cb stack as it does not provide fcntl locks
ocfs2 should detect and utilize the running stack, which in my case would be
cman
however, ocfs2 only works with o2cb stack, this is not the expected
5 matches
Mail list logo
