[Gluster-devel] 2.0.0 Finally Happened?

[Gordan Bobic]

Thanks for pointing it out. Since these issues were mentioned:

1) Self-heal of a file that does not exist on the first subvolume

Is this affected by read-subvolume and favourite-child options? Does 
this lead to the file being clobbered on "ls -la", since the directory 
metadata is going to be inconsistent (at least different modification 
time since a file was created on one of the secondary nodes)? Is there a 
way to heal this file without knowing it's name (and knowing it's name 
isn't always feasible if it becomes invisible once the primary server 
comes back up!)? If it shows up at least on the server where it exists, 
then doing a periodic "ls -laR" would heal it, but if it never shows up 
then it can't be healed - and in that case what happens when the file is 
appended or truncated for writing?

3) File re-opening after a server comes back up

Does the replication get kickstarted by doing a "ls -laR" to initiate 
self-healing even if a file is still being open and another server has 
rejoined? Will replication then continue online for currently open files?

Thanks.

Gordan


On 04/05/2009 21:49, ender wrote:
> Also you might want to check here.
>
> http://gluster.org/docs/index.php/Understanding_AFR_Translator#Known_Issues
>
> Gordan Bobic wrote:
>> Is there a changelog from rc9?
>> Has the 1st access bug been fixed?
>>
>> Gordan
>>
>>
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>