Client side afr, locking, race condition, simultanous writes, out of sync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok there are two threads on this and I am trying to wrap my head around it.

So a simple 2 server, 2 client, client side afr setup.

The clients at the SAME time do:

client1 # echo "one" > file.txt
client2 # echo "two" > file.txt

Are the threads regarding this and the conclusion at this point saying
that this is safe or not? Are we going to end up with server1 having
"one" and server2 having "two" or vice versa or the chance of, because
there is no "locking "mechanism" to know that two writes are happening
at the same time?

Should one or the other happen first, I would think either two would
be written on both and then one, or the other way around? Are we
saying this is not true?




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux