On Thu, Apr 28, 2011 at 04:16:51PM +0200, Martin Schenker wrote: > After triggering manually with "touch" using the right *CLIENT* > mount points, the self-heal/sync function worked fine. I was using > the server mounts before, as shown by the getfattr output. Not > good... > > Now the question remains WHY the Gluster system didn't do anything > on it's own? Is this a "healthy" situation and we shouldn't worry? Would it be good practice to regularly run a script to trigger any self-healing that might be necessary - or to test if necessary (how?) and then run on that condition? It would be easy, for instance, to use Python's os.walk function to run through and touch - or whatever - every file in the space. That adds a non-trivial load to a system, but for systems with load to spare, would running that say every hour, or every day, but good practice? Whit
