I am curious, is client side AFR susceptible to race
conditions on writes? If not, how is this mitigated?
In other words, what prevents conflicts when client A
& B both write to the same file? Could A's write to
subvolume A succeed before B's write to subvolume A,
and at the same time B's write to subvolume B succeed
before A's write to subvolume B? If so, isn't this
somewhat similar to a split brain operation? Is there
some form a transaction layer using file version #s
that prevents this?
Thanks for any info you could shed on this,
-Martin
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
