similar to: [PATCH] Bug fix for file comparison

Displaying 19 results from an estimated 19 matches similar to: "[PATCH] Bug fix for file comparison"

2016 Jul 25
2
[Bug 12036] New: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior
https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:
2010 Jun 15
3
about rsyncing of block devices
Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.
2008 May 08
1
Patch to not modify files in place unless "--inplace" option specified
Skipped content of type multipart/alternative-------------- next part -------------- diff -urN rsync-3.0.2-orig/generator.c rsync-3.0.2/generator.c --- rsync-3.0.2-orig/generator.c 2008-03-28 10:30:11.000000000 -0700 +++ rsync-3.0.2/generator.c 2008-05-07 15:35:08.317364774 -0700 @@ -1508,6 +1508,7 @@ if (preserve_links && S_ISLNK(file->mode)) { #ifdef SUPPORT_LINKS + int iflags =
2015 Sep 14
3
[Bug 11521] New: rsync does not use high-resolution timestamps to determine file differences
https://bugzilla.samba.org/show_bug.cgi?id=11521 Bug ID: 11521 Summary: rsync does not use high-resolution timestamps to determine file differences Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core
2005 Jul 31
1
I think I found a bug...
I am looking at rsync 2.6.6 When I try to rsync a directory using --link-dest it never creates hardlinks. After crashing my way through the code here is what I found: generator.c: function 'unchanged_file' if (ignore_times) return 0; return cmp_modtime(st->st_mtime, file->modtime) == 0; shouldn't these lines be: if (ignore_times) return 1;
2013 Jan 22
0
rsync - using a --files-from list to cut out scanning. How to handle deletions? (fwd)B
Paul Wayne, Kevin, Teodor and others, Thanks for your contributions in response to my postings. Paul: I was very imprecise if not plain wrong in my description. :-( Thanks for explaining what really happens. > "Rsync will not update an existing file in-place unless you use the > --inplace option. So --whole-file is irrelevant for this. > Rsync (without --inplace) will always
2013 Jan 23
0
Changed attributes for a file in destination that is hard linked get propagated to --link-dest directories
Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled
2008 Jul 29
7
DO NOT REPLY [Bug 5644] New: Option to recheck basis dirs for existing dest files
https://bugzilla.samba.org/show_bug.cgi?id=5644 Summary: Option to recheck basis dirs for existing dest files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:
2010 Apr 14
0
issues with batch mode for incremental backups
Hi! I use rsync batch mode for incremental backups. That is, I create an on-line backup with rsync, and use the --write-batch flag to additionally generate my delta, which I send off-site. To restore, I download a full backup and apply the deltas with --read-batch. This is quite a lovely setup, in principle. However, restore has give me problems. Before I detail them, let me ask: Are a lot
2005 Mar 31
2
Some files not logged when using --compare-dest. Bug?
Hi again. I just spotted another peculiarity when inspecting the rsync log. When using --compare-dest, source files that have permissions that differ from the "comparables" are not logged, unless you're using -i. Here's a testing session: $ ls -lR .: total 12 drwxr-xr-x 2 vidar users 4096 2005-03-31 14:16 cmp/ drwxr-xr-x 2 vidar users 4096 2005-03-31 14:23 dst/
2005 Jan 31
1
[patch] add "--ignore" option
Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both
2007 Oct 30
3
Rsync hard-links devices with different mtimes despite -t: expected?
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
2008 Oct 09
1
DO NOT REPLY [Bug 5820] New: rsync does not replace symlink atomically
https://bugzilla.samba.org/show_bug.cgi?id=5820 Summary: rsync does not replace symlink atomically Product: rsync Version: 3.0.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: rsync@sysoev.ru
2005 Apr 23
1
--link-dest / --hard-links problem
I've looked around for a bug report on this problem and haven't seen one, so I apologize if this has already been discussed. I have a homegrown script which uses rsync to maintain daily backups of roughly twenty Redhat Linux systems running RH 7.2, 7.3, AS 3, and AS 4. As there are files with multiple links on the source systems, it is necessary to call rsync using the -H (--hard-links)
2006 Oct 21
1
Rsync 2.6.9pre2 tries to read ACLs of nonexistent files
Dear rsync people, Today I tried to back up my computer using rsnapshot with the RPM version of rsync-acl 2.6.9pre1 that I built. I tried twice, and both times, rsync encountered some kind of assertion failure. I was trying to reproduce the crash with rsync-acl 2.6.9pre2 and noticed a different bug (described below); when I have a chance, I will go back and investigate the crash further. Rsync
2023 Jul 03
0
[PATCH] Add option --log-after to log after moving file into place
This mode is useful when a process is monitoring the log for post-processing of transferred files. With --log-after in local mode, both sender and receiver log to the same log file, so it require --log-file with absolute path. We add %o to the default log format, so it will be easy to tell the logs of the sender from the logs of the receiver: 2023/02/14 14:40:25 [559755] building file list
2004 Dec 27
3
how to debug frame slips?
Hi, I'm running into issues receiving faxes which, from what I have read, may be caused by frame slips. While I can find many posts saying to investigate it, I can't find any that describe *how* to debug the problem. Tried searching this list as well to no avail. Any pointers would be greatly appreciated. FYI, I'm running wbel, AMP 1.04, spandsp 2pre4. Faxing to a pstn on a
2007 Sep 22
0
rsync build on IA64 using icc
I got numerous warnings when building rsync on IA64 (Itanium-2) using Intel C/C++ compiler (see attached). Is this expected? Thanks, Michael -------------- next part -------------- Script started on Fri 21 Sep 2007 06:14:05 PM BST ~/src$ ls -alt total 222884 -rw-r--r-- 1 mccssmb2 mcc101 0 Sep 21 18:14 build_rsync drwxr-xr-x 8 mccssmb2 mcc101 4096 Sep 21 18:14 . -rw-r--r-- 1
2013 Dec 13
0
[PATCH v4 RFC 2/3] virtio: introduce 'device_lost' flag in virtio_device
This flag should be set by a virtio transport driver, when it was notified about a lost device, before the remove callback of a backend driver is triggered. A backend driver can test this flag in order to perform specific actions that might be appropriate wrt the device loss. In case of a device loss further request queueing should be prevented by setting appropriate queue flags prior to