Re: [MooseFS-Users] rsync from moosfs chnages source file time stamps

[Jakub Kruszona-Z. <jak...@ge...>]

On 21 Apr, 2016, at 16:33, Valeri Galtsev <ga...@ki...> wrote:

> Dear Experts,
> 
> I have sort of weirdness I just stumbled over.
> 
> I migrates some directories to moosefs (free opes source version, standard
> installation "by the book" on FreeBSD). At some point I decided to migrate
> the directory back to local (UFS) filesystem on the machine. Here is
> weirdness I observe:
> 
> after i run
> 
> rsync -avu /path/do/mfs/mount/directory /path/to/local/fs
> 
> I do get the content of directory on local filesystem as expected with all
> correct file attributes (user/group ownership, creation time, content).
> However, the source files on moosefs change their time stamps, as if the
> report last access time instead of creation time. They were reporting
> correct creation times after they were rsync'ed from local filesystem to
> moosefs originally. This basically renders rsync command useless (and
> damaging if you care about file creation times) when you rsync from
> moosefs (elsewhere).
> 
> What am I doing wrong? I've used Linux and Unix for over decade an a half,
> ans used rsync over comparable period of time. What I hit with moosefs
> gives me kind of shock, and I can't figure myself what could I be doing
> wrong.
> 
> Thanks in advance for all your advices.
> 
> Valeri

We have changed atime/mtime management in MooseFS recently (in version 3.0.74), so the question is which version of MooseFS do you use?

It looks like a bug in MooseFS, so we need the version, because we have two options here.
The bug was in previous atime/mtime mechanism (pre 3.0.74) or there is a bug in current mechanism.

-- 

 \_\            /_/
    \_\_    _/_/
        \--/
        /Oo\_--____
       (__)        )
        ``\    __  |
           ||-~  `||
           ||     ||
           ""     ""

Regards,
Jakub Kruszona-Zawadzki