I noticed that the heal process was not triggered after I upgraded the
3rd (out of 3) node.
Running " # for i in `gluster volume list`; do gluster volume heal $i;
done " didn't trigger any intracluster activity ..
On Tue, Dec 13, 2016 at 5:41 PM, Joe Julian wrote:
>
>
> On 12/13/2016 08:00 AM, M
On 12/13/2016 08:00 AM, Momonth wrote:
Are you even using nfs-ganesha?
If not, start by deleting glusterfs-ganesha, then run the update.
Not at the moment, however it was deployed and tested previously.
I worked it around as follows:
# yum remove glusterfs-ganesha-3.8.5-1.el6.x86_64
# yum u
>
> Are you even using nfs-ganesha?
>
> If not, start by deleting glusterfs-ganesha, then run the update.
Not at the moment, however it was deployed and tested previously.
I worked it around as follows:
# yum remove glusterfs-ganesha-3.8.5-1.el6.x86_64
# yum update glusterfs
Should I wait till
On 12/13/2016 09:44 AM, Momonth wrote:
Hi,
I tried to run an upgrade, following the docs -
http://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgrade_to_3.9/
But it fails with the following:
..
--> Finished Dependency Resolution
Error: Package: glusterfs-ganesha-3.9.0-2.el6.x86_64 (gluster-
Hi,
I tried to run an upgrade, following the docs -
http://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgrade_to_3.9/
But it fails with the following:
..
--> Finished Dependency Resolution
Error: Package: glusterfs-ganesha-3.9.0-2.el6.x86_64 (gluster-3.9)
Requires: /usr/lib/ocf/re
