Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report to
verify it still requires effort and occurs on an Ubuntu release in standard
support, and it does not.
It is unfortunate that we were unable to
I can't believe this bug still exists in Ubuntu 12.04 LTS. Is OCFS2 so
rarely used that this bug has no importance to the package mantainers?
Please consider raising the severity to something more than low.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I can't believe this bug still exists in Ubuntu 12.04 LTS. Is OCFS2 so
rarely used that this bug has no importance to the package mantainers?
Please consider raising the severity to something more than low.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi, i'd like to help to fix this problem. Right now i've stopped my
openstack deployment because of this bug. I'll try to write a o2cb
upstart script to boot, then i'll go for the ocfs2 script. If anyone
wants to help, just let me know! Thanks
--
You received this bug notification because you
Hi, i'd like to help to fix this problem. Right now i've stopped my
openstack deployment because of this bug. I'll try to write a o2cb
upstart script to boot, then i'll go for the ocfs2 script. If anyone
wants to help, just let me know! Thanks
--
You received this bug notification because you
Hi,
Has anyone made this upstart scripts available?
I'm not sure this bug should have its importance set to 'Low' : the present
behaviour makes the difference between a working and a non working cluster node
in case of reboot. It's not a detail.
--
You received this bug notification because
Hi,
Has anyone made this upstart scripts available?
I'm not sure this bug should have its importance set to 'Low' : the present
behaviour makes the difference between a working and a non working cluster node
in case of reboot. It's not a detail.
--
You received this bug notification because
ocfs2-tools probably be needed to converted to upstart.
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided = Low
** Changed in: ocfs2-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
ocfs2-tools probably be needed to converted to upstart.
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided = Low
** Changed in: ocfs2-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This still seems to be a problem in Lucid. We've moved from Hardy (no
problems automounting OCFS2 over iSCSI from there) but on Lucid the o2cb
service has never started the cluster when the machine is booted and
then as a consequence mountall-net fails to mount the drive.
--
mountall-net tries
This also affects hardy using the classical SysV init style
Even more severe, the o2cb is stopped before the ocfs2 filesystems are
unmounted.
Other machines that use the same OCFS2 volume then will need to fence
theirselfes and hence will panic or reboot, see
11 matches
Mail list logo
