Hide Forgot
Reported by "Stephan von Krawczynski" <skraw>: The servers (2) are configured: volume posix type storage/posix option directory /p3 end-volume volume locks type features/locks subvolumes posix end-volume volume p3 type performance/io-threads option thread-count 8 subvolumes locks end-volume volume server type protocol/server option transport-type tcp option auth.addr.p3.allow * subvolumes p3 end-volume The clients (2) are both: volume remote1 type protocol/client option transport-type tcp option remote-host 192.168.0.101 option remote-subvolume p3 end-volume volume remote2 type protocol/client option transport-type tcp option remote-host 192.168.0.102 option remote-subvolume p3 end-volume volume replicate type cluster/replicate option data-self-heal on option metadata-self-heal on option entry-self-heal on subvolumes remote1 remote2 end-volume volume readahead type performance/read-ahead # option page-size 1MB # unit in bytes option page-count 8 # cache per file = (page-count x page-size) subvolumes replicate end-volume volume writebehind type performance/write-behind # option aggregate-size 1MB # option window-size 1MB option cache-size 128MB option flush-behind on subvolumes readahead end-volume volume cache type performance/io-cache option cache-size 512MB subvolumes writebehind end-volume To test healing we copy some directories on server1 /p3, then let client 1 do an ls -lR. When this ends all files and dirs have appeared on server2, but all dirs have timestamps from actual creation and not the originals from server1. Whereas all files have correct timestamps.
Patch submitted: http://patches.gluster.com/patch/688/