- Original Message -
> From: "Alan Millar" <grunthos...@yahoo.com>
> To: "Anuradha Talur" <ata...@redhat.com>
> Cc: gluster-users@gluster.org
> Sent: Wednesday, March 2, 2016 2:00:49 AM
> Subject: Re: [Gluster-users] Broken after 3.7.8 upgrade
> The "unable to get index-dir on .." messages you saw in log are not
> harmful in this scenario.
> A simple explanation : when you have 1 new node and 2 old nodes, the
> self-heal-deamon and
> heal commands run on the new node are expecting that the index-dir
> "/.glusterfs/xattrop/dirty"
- Original Message -
> From: "Alan Millar" <grunthos...@yahoo.com>
> To: "Anuradha Talur" <ata...@redhat.com>
> Cc: gluster-users@gluster.org
> Sent: Wednesday, March 2, 2016 2:00:49 AM
> Subject: Re: [Gluster-users] Broken after 3.
>> I’m still trying to figure out why the self-heal-daemon doesn’t seem to be
>> working, and what “unable to get index-dir” means. Any advice on what to
>> look at would be appreciated. Thanks!
>At any point did you have one node with 3.7.6 and another in 3.7.8 version?
Yes. I upgraded each
On Feb 29, 2016, at 5:43 PM, Alan Millar wrote:
> > I have tried with entry-self-heal/metdata-self-heal/data-self-heal set both
> > on and off; neither seems to make a difference.
>
> Correction: setting these to ON does fix the actual replicated data. I
> checked
> I have tried with entry-self-heal/metdata-self-heal/data-self-heal set both
> on and off; neither seems to make a difference.
Correction: setting these to ON does fix the actual replicated data. I checked
with md5sum on various files on both bricks, and it matches.
But it does not fix the