similar to: [Bug 13385] New: rsync sometimes silently transfers more or fewer mtimes than it should

https://bugzilla.samba.org/show_bug.cgi?id=12742 Bug ID: 12742 Summary: a proposal: fix bogus nanosecond mtimes on transfer (patch included) Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod

Hello again, as stated earlier there is a problem with mtime setting on directories during healing in replication setup. Today I tested 2.0.5 and found out that the handling is more or less generally buggy for directory mtimes. Simply try this: untar some kernel archive on your local disk and look at the mtime of the created top directory. now untar the same archive on an exported gluster fs and

BAADCAAHDwEHEAEKFwESKwIXNQIaOwIcQQIgSQIpXwM4gAQ8igU/kAVAkwVB lAVClwVCmAVFngVJpgZKqQZLrQZPtQZQtgZRuQYAAAAAAQB1lW3cAAAAAXRS TlMAQObYZgAAAAFiS0dEAIgFHUgAAAAJcEhZcwAALiMAAC4jAXilP3YAAAAH dElNRQfXAxgNAiAQYlKOAAAAHXRFWHRDb21tZW50AENyZWF0ZWQgd2l0aCBU aGUgR0lNUO9kJW4AAADMSURBVEjHzZbJEsMwCEPpvjfdW9T//89OkktqVxgy PpSjzLPHQeCIZKGDkGJoFsF0E1EW0XyCaFVA/fl3RvzaTfW6nPTaaQqWP1TP

Hi, I'm running the following command as a local copy command. faheem at bulldog:/mnt/data$ sudo rsync -abvz --super /data/ . Origin directory faheem at bulldog:/data$ ls -la total 28 drwxr-xr-x 7 root root 4096 Jun 26 08:34 . drwxr-xr-x 25 root root 4096 Apr 13 17:09 .. drwxr-xr-x 2 owzar001 root 4096 Nov 6 2010 CTS drwxr-xr-x 2 owzar001 owzar001 4096 Aug 27 2010

Hi all. I have the following problem building kde-window-decorator (compiz 0.5.2 and 0.6.2): Making all in kde make[2]: Entering directory `/usr/src/RPM/BUILD/compiz-0.6.2/kde' Making all in window-decorator make[3]: Entering directory `/usr/src/RPM/BUILD/compiz-0.6.2/kde/window-decorator' i586-openmamba-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -I../../include -I/usr/include/dbus-1.0

https://bugzilla.samba.org/show_bug.cgi?id=5867 Summary: rsync with ACLs resets mtime on targets Product: rsync Version: 3.0.4 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: samba@byshenk.net

I've tried lots and lots of stuff, fiddling with the various configuration options again and again. Solitaire works most of the time. Notepad doesn't let me enter text. Calc displays the numbers in the wrong place, but otherwise works. Street Atlas USA 8.0 barfs completely. Not even close, in spite of being in the database. Agent does not exhibit proper internal windowing behavior,

try /sbin/depscan.sh --update

Dear All, Along with the files that suddenly disappear, we have a bit of a problem with these that do not. Namely, in my test runs I can see a small but stable set of files, that rsync is repeatedly trying to transfer, and then repeatedly fails to updates their times ; and then the story repeats itself. The situation is illustrated by the log snippet below, where I have changed file names to

On the wiki: http://wiki.dovecot.org/Plugins/Zlib I think there should be a step 5.0. along the lines of "get and remember the original message file's mtime" And a step 5.4 like "Using the touch command or some other method, set the now compressed message's mtime back to the mtime of the original message file." To preserve the message's internal time in case

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

> Dovecot doesn't look at the new files' mtimes or ctimes, because that > would require stat()ing the file, which slows it down. So it's using > the timestamp in the Maildir filename itself. Thanks Timo for the clarification. Whats Dovecot's strategy when the file-name does not contain a time-stamp and its just a sequential long number such as 1494829006737776656. My

Hi all. I prepared a mirror (that is intended to be updated by rsync) by doing the initial copy using cpio (for efficiency on 15 million files). Unfortunately, user, group, and mtime of some directories and files was copied incorrectly. Can I use rsync (GIT) to fix this? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

Hello List, How would i rsync all files which are older than X-Days? I am missing some kind of -mtime option. Since this is quite common for backups i am wondering how you are doing this kind of stuff. Thanks, Mario

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

I thought I'd send this here too, since I spent so much time writing it as comment to maildir-sync.c :) Now only thing left to do is to write the code to match it. /* Here's a description of how we handle Maildir synchronization and it's problems: We want to be as efficient as we can. The most efficient way to check if changes have occured is to stat() the new/ and cur/

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The ctime will always be newer or the same as the mtime. This is because changing the mtime also changes the ctime as does other things like changing the permissions. Rsync only pays attention to the mtime because rsync can set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model.

> On 17 Oct 2015, at 11:44, Akash <akbwiz+dovecot at gmail.com> wrote: > >> Dovecot doesn't look at the new files' mtimes or ctimes, because that >> would require stat()ing the file, which slows it down. So it's using >> the timestamp in the Maildir filename itself. > > Thanks Timo for the clarification. Whats Dovecot's strategy when the