[Gluster-users] Unexpected AFR self-heal behavior (file contents not synced).

[Krishna Srinivas]

Matthew,

Since you had incorrect vol files to start with, you need to start
your testing steps afresh with correct vol files. Remove the files in
the backend and repeat the steps once again and see if it works fine.

Krishna

On Thu, Mar 12, 2009 at 8:35 PM, Matthew Davis <mdavis at helius.com> wrote:
> Thank you, that helped. Changing the order, I now have the expected data everywhere except in the backend directory on server B.  When I cat the backend files on server B I get file x with the original content (not updated) and file y is there but empty.  The client mount point on both machines shows the correct updated file contents (as does the backend on server A).
>
> The only attributes set on the backend files now are "trusted.glusterfs.afr.data-pending=0x0000000000000000". This is the same for all files on both sides. Should there be create time and version attributes there (this is on 2.0rc4)? I'm wondering if I've got something funny going on there.
>
> Thanks,
> Matthew Davis
>
> On Thu, Mar 12, 2009 at 01:12:27PM +0530, Vikas Gorur wrote:
>> 2009/3/11 Matthew Davis <mdavis at helius.com> wrote:
>> <snip>
>>
>> In your configuration, the order of subvolumes of replicate on A and B
>> is not the same. It is crucial that this rule be followed. So the
>> correct configuration would be:
>>
>> Server A:
>>
>> volume replicate
>>   subvolumes data-locks twin-data-locks
>>
>> Server B:
>>
>>  volume replicate
>>   subvolumes twin-data-locks data-locks
>>
>> Vikas
>> --
>> Engineer - Z Research
>> http://gluster.com/
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>