On 10/13/2012 09:53 AM, Brian Candler wrote: > Anyway, I think my question is answered. Normally I would create a file as > xxx.tmp, sync and then rename it to xxx, to protect against a > partially-created file; but for large files this looks like it's not a good > approach for glusterfs with a distributed volume. It adds one level of inefficiency during a lookup() as the hash will point to a different subvolume which will return the sticky pointer causing an additional query to the correct subvolume. Size of the file has no effect.
