On Mon, 13 Jul 2009 08:05:03 -0500 (CDT)
Vikas Gorur <vi...@gluster.com> wrote:

> 
> ----- "Stephan von Krawczynski" <sk...@ithnet.com> wrote:
>  
> > Sorry to say that. But if I rsync the trees they end up with _correct_
> > (i.e. identical) timestamp displayed at standard "ls".
> > Whereas using self-heal shows different timestamps on "ls".
> > This at least proves that the stamps I mean are settable by user-space
> > tools (like rsync).
> 
> Please clarify what you mean by "timestamp". As you know, there are
> three timestamp values, not one. And by "different", do you mean
> the timestamps are different on different servers, or that mtime and ctime
> are different on a single server?
> 
> Vikas

To make things even clearer visible, please take a look at this:

Stat of directory "suse" on the first server, note mtime:

linux-zd3t:/p3 # stat suse
  File: `suse'
  Size: 96              Blocks: 0          IO Block: 4096   directory
Device: 804h/2052d      Inode: 4           Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2009-07-13 12:49:12.000000000 +0200
Modify: 2009-06-04 20:22:57.000000000 +0200
Change: 2009-07-13 12:44:25.000000000 +0200


Stat of directory "suse" on the second server after self-heal:

linux-tnpx:/p3 # stat suse
  File: `suse'
  Size: 96              Blocks: 0          IO Block: 4096   directory
Device: 804h/2052d      Inode: 9           Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2009-07-13 12:49:23.000000000 +0200
Modify: 2009-07-13 12:44:03.000000000 +0200
Change: 2009-07-13 12:44:03.000000000 +0200

Obviously mtime is _not_ correctly set. 

-- 
Regards,
Stephan


_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users

Reply via email to