Gluster users - Jun 2010 - Replication conflict

Hi the list,

I'm using gluster 3.0.4 in a replication mode on ext4 partition over 2
servers (RedHat).
I have 2 clients accessing the datas for reading/writting.

on the clients, I saw this message:
[2010-06-15 15:51:28] W [fuse-bridge.c:491:fuse_entry_cbk] glusterfs-fuse:
LOOKUP(/path/to/file)
inode (ptr=0x95c5b48, ino=6030540, gen=5467342176369251050) found
conflict (ptr=0x7f2782d0, ino=6030540, gen=5467342176369251050)
>From my understanding, it's a Warning, saying that my FS might be
un-synchronized.
Am I right?
Did gluster auto sync the file?
Do you have an idea what could have generated this message?

Thanks for your help.

cheers

On Wednesday 23 June 2010 05:51 PM, Bedis 9 wrote:
> on the clients, I saw this message:
> [2010-06-15 15:51:28] W [fuse-bridge.c:491:fuse_entry_cbk] glusterfs-fuse:
> LOOKUP(/path/to/file)
> inode (ptr=0x95c5b48, ino=6030540, gen=5467342176369251050) found
> conflict (ptr=0x7f2782d0, ino=6030540, gen=5467342176369251050)
>
> > From my understanding, it's a Warning, saying that my FS might be
> un-synchronized.
> Am I right?
> Did gluster auto sync the file?
>    
This has got nothing to do with FS being unsynchronized.
> Do you have an idea what could have generated this message?
>
>    
This is a benign warning. If there are hardlinks or rename operations 
happening, this message can be seen.
If you do not notice any functional impact, you can ignore this message.

Regards,
Vijay