similar to: Caching {filePath,mtime64,checksum} values to speed up execution-time

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

Hi everybody, Until know i synchronized a few directories full of binaries with "--checksum" options, it took each time a lot of time since rsync "mdsum" each file contained in my directories. Then I decided to skip "--checksum" option to let rsync work only of files size and files mtime and speed up the process but when i launch a dry-run : rsync wants to

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

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

I am working with rsync on Debian, package version 3.0.9-1. I am trying to use rsync --compare-dest to make a delta-copy of a directory. In my case, the mtimes are all unreliable. The data is the same, but the times are all messed up and always will be. I am trying to use --compare-dest with --checksum or --size-only and it does not work. All files are transferred and the delta copy

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:

This is a suggestion for adding to rsync an option "--checksum-path=PROGRAM". Once this option is given, provided it is accompained by option "--checksum", both the receiving and sending side of rsync would compute checksums calling PROGRAM, instead of the usual checksum program. Why is this usefull? Suppose I have two collections of MP3 files at different locations which I

Hello all. Our system consists of two linux machines, each running Red Hat 7.1 (kernel 2.4.9-34), using SMB to mount multiple shares hosted by a Windows 2000 Advance Server. smbclient from Samba 2.2.5 is used to do the actual mounting. Over the weekend, a number of files on these SMBFS shares were created with incorrect timestamps (modification times). In some cases, the timestamps were off by

Hi, I just want some clarification on how Dovecot's IMAP assigns UIDs when it picks files from the "new" directory of a Maildir. What I am observing is that only ctime has a role to play in it. For example if there are two files in "new", a.msg & z.msg. Even when a.msg has lower mtime than z.msg and "a" comes before "z" alphabetically, dovecot

notice: /subject.sol1.net/virtual_mail_server/File[/etc/postfix]/checksum: checksum changed ''{time}Thu Jan 25 16:31:08 EST 2007'' to ''{time}Thu Jan 25 16:36:39 EST 2007'' I know there''s something weird in the directory modification detection that causes the next run after things actually change to suffer from this problem, but I''m getting it

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

Hi, I'm wondering why when I use --size-only on the same file, except the modification time, rsync transfers the modification time? I was under the impression that --size-only caused rsync to transfer files based upon differences in the size of the file. For example: #cp Untitled.pdf Untitled-2.pdf #touch Untitled.pdf #rsync -ani --size-only Untitled.pdf Untitled-2.pdf .f..t......

I have a question which others must have encountered. I switched from uw-imap to dovecot-imap a few months ago and moved my fairly large mail archive (~15 yrs) by simply mounting both accounts in a mail app and simply copying my folders over. This worked well, and all my mail is in order when I view it in evolution or thunderbird on any number of machines. However, since our company uses MS

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

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

sorry for the confusing subject line. i couldn't think of a better way to say it. i'm wondering if rsync can perform the following action: Compare contents of Directory A (master) to Directory B and copy any differences from Directory A to Directory C (example below) Directory A: foo bar biz nis sum tin Directory B: foo biz nis sum Directory C: (empty prior to rsync operation) bar

FYI this topic was crossposted to Gentoo forums (http://forums.gentoo.org/viewtopic-t-845865.html) Hello, Yesterday I updated Wine from 1.3.2 to 1.3.3 and today when I wanted to use a program through Wine (a text editor, but it doesn't really matter) I received an error that some files could not be found. The filepath given in the error message was wrong, instead of reading something like

I've reproduced on ubuntu and winodws with R3.4.3 When the filepath contains a tilde, the result is NA. But if the file path is expanded then the function works. Example: tools::md5sum("~/.Rprofile") returns NA tools::md5sum(normalizePath("~/.Rprofile")) returns the proper md5 Perhaps this is expected behaviour because the documentation does say NA is returned for

> 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

I'm trying to understand the point of the --checksum-seed option. As I understand it from a little reading, checksums are not cached over executions of rsync. So...what is the point of fixing the seed? Is this in support of patches which *do* support caching of checksums? I've read about caching these in files and in xaddr. Is there a "best solution" for caching