Early indications are that setting "option metadata-change-log on" for
cluster/replicate is a likely workaround for the mtime issue. I'll start
over, and see if the issue is truly gone with this option in place...
It might be worth considering defaulting this option to "on".
Thanks,
Brent
On Wed, 13 May 2009, Brent A Nelson wrote:
On Wed, 13 May 2009, Brent A Nelson wrote:
With regards to the incorrect modification time appearing on some files, I
note the following:
ls -l on Node1 in a mirror:
-r--r--r-- 1 root root 40280 2008-03-17 12:03
/disk1/glusterfs/tftpboot/hardy64/pool/main/t/tasksel/tasksel-data_2.70ubuntu4_all.deb
Node 2 in the same mirror:
-r--r--r-- 1 root root 40280 2009-05-12 19:40
/disk1/glusterfs/tftpboot/hardy64/pool/main/t/tasksel/tasksel-data_2.70ubuntu4_all.deb
It appears that 1/2 of the mirror set the modification time correctly, but
the other half did not.
Just a bit of additional info. It appears that the first half of the mirror
has correct mtimes. The second half of the mirror has wrong mtimes on all
files, but directory mtimes are fine. When you go to view the mtimes on the
GlusterFS, sometimes you will get the mtime from one node, sometimes the
other, hence the seeming randomness.
Also, I see that zero-length files have correct mtimes on both halves of a
mirror.
Thanks,
Brent
