Brent, I understand what is happening. It is because I/O threads lets the mtime overtake the write call. I assume you have loaded io-threads on server side (or below write-behind on client side). I could provide you a temporary 'ugly' fix just for you if the issue is critical (until the proper framework comes in 1.4) regads, avati On Thu, Apr 26, 2007 at 10:57:20PM -0400, Brent A Nelson wrote: > Setting "option aggregate-size 0" does not eliminate the mtime glitch > 100%. Copying /usr to an afr/unify glusterfs, I found that almost > everything was okay, but a handful of files on one server had updated > mtimes, and a different handful on the other server did, as well. > > So, even with aggregation out of action, write-behind will still > occasionally alter mtimes on a "cp -a". > > Thanks, > > Brent > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- ultimate_answer_t deep_thought (void) { sleep (years2secs (7500000)); return 42; }
