Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck:
----- Original Message -----
From: "Simon Barrett" <Simon.Barrett@tradingscreen.com> To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node
I am working through the setup of oVirt node for a 3.4.1 deployment.
I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained.
Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot?
Many thanks,
Simon
Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster.
Ryan / Fabian- thoughts?
Hey,
I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents.
But Simon, can you give details which configuration files are missing and why glusterd is not starting? Is glusterd starting? I'm getting the impression that it's starting, but
On 05/26/2014 04:14 AM, Fabian Deutsch wrote: that it has no configuration. As far as I know, Gluster keeps most of the configuration on the brick itself, but it finds brick information in /var/lib/glusterd. The last patch simply opened the firewall, and it's entirely possible that we need to persist this. It may be a good idea to just persist the entire directory from the get-go, unless we want to try to have a thread watching /var/lib/glusterd for relevant files, but then we're stuck trying to keep up with what's happening with gluster itself... Can we
Thanks fabian
Either way I suggest you take a look in the below link- http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting...
Let s know how it works.
Doron