[Gluster-users] Replication Issue

[Jenn Fountain]

On Sep 22, 2010, at 6:33 PM, Jenn Fountain wrote:

> On Sep 22, 2010, at 6:19 PM, Bernard Li wrote:
> 
>> Hi Jenn:
>> 
>> [Replying back to the mailing-list]
>> 
>> On Wed, Sep 22, 2010 at 3:06 PM, Jenn Fountain <jfountai at comcast.net> wrote:
>> 
>>> Yes, but it only replicates subdirectories and all of their content but not files.
>>> 
>>> IE:
>>> 
>>> [root at stag02 upload]# ls -la
>>> total 1140
>>> drwxr-xr-x 69 xx xx 589824 Sep 22 14:42 .
>>> drwxrwxr-x 39 xx xx  16384 Sep 22 14:34 ..
>>> drwxr-xr-x  6 xx xx   4096 Feb 16  2010 lo_273 <-- replicated
>>> -rw-rw-r--  1 xx xx    8398 Sep 10  2007 nplantsmall.jpg <-- not replicated
>> 
>> That's kind of odd, perhaps you can post snippets of your log file for
>> the developers to see.
>> 
>> P.S. It probably is a typo but the command you should be using is "ls
>> -alR" (you didn't have -R above).  Have you also tried `find`?
>> 
>> Cheers,
>> 
>> Bernard
> 
> Sorry, I didn't realize I just hit reply.
> 
> yes, I am using ls -alR and find . -name "*"
> 
> This is just the common theme of the log:
> 
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode
> [2010-09-22 18:22:17] E [afr.c:107:afr_set_split_brain] replicate: invalid argument: inode

Well, it appears a reboot of all servers resolved the issue.

> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users