I'm not sure whether it's an issue or not anymore. I discontinued using
gfs2 because I could not get the kernel panic to go away.
Dave Spano
- Original Message -
From: "Christopher M. Penalver"
To: dsp...@optogenics.com
Sent: Monday, December 30, 2013 4:12:
I used the block_device_mapping table to figure out what to rename.
Just throwing that out there for people who need to change their
existing volumes before a fix is put out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
In this mailing list response, Vish says you can use
export OS_NO_CACHE=1 in your .bashrc to stop this behaviour.
https://lists.launchpad.net/openstack/msg16095.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Thank you Clint. I'm using ceph also, and was interested in a solution
to this problem as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028718
Title:
nova volumes are inappropriately clingy f
q(ghs);
out_parent:
gfs2_holder_uninit(ghs);
return error;
}
Dave Spano
Optogenics
Systems Administrator
- Original Message -
From: "Bart Verwilst"
To: dsp...@optogenics.com
Sent: Tuesday, August 21, 2012 8:26:22 AM
Subject: [Bug 1020207] Re: gfs2 kernel oops when dele
Public bug reported:
I have an active/active drbd cluster with pacemaker running on cman. If
I create a file on the shared gfs2 file system on one node, then try to
delete it on the other, I'm receiving this kernel panic. I get the same
error on both nodes, so it's not specific to either machine.
I found this in a blog posting found here: http://blog.init.hr/?p=186.
Important: We’ve encountered couple of bugs that are in the queue for
fixing. If you are using or have a desire of using cLVM, please do not
use 12.04 yet. Once these fixes land into archives, we’ll send an email
to ubuntu-ha m
