search for: touch_up_dir

Displaying 9 results from an estimated 9 matches for "touch_up_dir".

Did you mean: touch_up_dirs
2008 Feb 25
0
Fwd: Making rsync compile under Mac OS X 10.3.9 with extended attributes
...yUX, 0xbfffca80); > PWD=/Volumes/Dst/80-rsync-test > name=.file-with-flags.CqNyUX > set modtime of Src/60-bsd-flags/.file-with-flags.CqNyUX to > (1203281916) Sun Feb 17 21:58:36 2008 > renaming Src/60-bsd-flags/.file-with-flags.CqNyUX to Src/60-bsd- > flags/file-with-flags > touch_up_dirs: Src/60-bsd-flags (11) > set modtime of Src/60-bsd-flags to (1203281916) Sun Feb 17 21:58:36 > 2008 > touch_up_dirs: Src/60-bsd-flags/dir-with-flags (22) > set modtime of Src/60-bsd-flags/dir-with-flags to (1203281916) Sun > Feb 17 21:58:36 2008 > recv_files(Src/60-bsd-flags/...
2008 Feb 02
2
hardlinks not working with inode number > 2^31
I've been using 3.0.0pre8 to move a Debian archive from one filesystem to another. This archive contains a daily snapshot of the Debian ftp site, with common files hardlinked to save space. I noticed that it was using far more space than necessary. Upon investigation it seems that all the source files that have inode numbers greater than 2^31 aren't being hardlinked together at the
2015 Dec 21
0
[Bug 11646] New: rsync incapable of copying corrupted filesystem
...der] flist start=58089, used=2, low=0, high=0 [sender] i=58089 <NULL> daily.1/usr/bin/ mode=040755 len=12,288 uid=0 gid=0 flags=4 [sender] i=58090 <NULL> daily.1/usr/bin/ mode=040755 len=12,288 uid=0 gid=0 flags=14 send_files(56588, daily.1/usr/bin) recv_generator(daily.1/usr/bin,56589) touch_up_dirs: daily.1/usr/bin (9080) recv_files(daily.1/usr/bin) [receiver] receiving flist for dir 9580 [generator] receiving flist for dir 9580 received 2 names removing duplicate name daily.1/usr/bin from file list (57337) [generator] flist start=57336, used=2, low=0, high=0 [generator] i=57336 3 daily.1/us...
2008 Mar 04
1
preserve ctimes of *unchanged* directories on receiver
'rsync -a' updates the ctime on a directory even if no file in that directory has changed. A kind of workaround is to use '-O', but then the mtimes of directories are not preserved. (Usage example where this is important: maintain a copy of filesystem A in filesystem B, and use filesystem B as the source for incremental backups (e.g., with star). rsync is run before an
2008 Oct 13
1
rsync hangs during --remove-source-files
...wed up and dir2 twice. This is on a dual core CPU with rsync version 3.0.4 protocol version 30. The log file shows no errors. Last 4 lines say: renaming dir/res/.svn/text-base/.somefile.svn-base.mDBdUb to dir/res/.svn/text-base/somefile.svn-base sender removed dir/.svn/text-base/somefile.svn-base touch_up_dirs: dir/.svn/prop-base (84) set modtime of dir/res/.svn/prop-base to (1223212308) Sun Oct 5 21:11:48 2008 Any suggestions how to debug this so that I can find out what's going on? Unfortunately I haven't found a way to reproduce it. Every time I kill and execute the same command again, it w...
2009 Jul 14
1
--delete not working (minimal example)
...nt=2 box2/ generator starting pid=4836 delta-transmission disabled for local transfer or --whole-file recv_generator(.,0) send_files(0, box1/.) recv_files(2) starting recv_generator(.,1) recv_generator(letter,2) letter is uptodate send_files(2, box1/letter) generate_files phase=1 send_files phase=1 touch_up_dirs: . (0) recv_files(.) recv_files(letter) recv_files phase=1 generate_files phase=2 send_files phase=2 send files finished total: matches=0 hash_hits=0 false_alarms=0 data=0 recv_files phase=2 generate_files phase=3 recv_files finished generate_files finished client_run waiting on 4836 sent 56 by...
2018 Apr 13
3
[Bug 13385] New: rsync sometimes silently transfers more or fewer mtimes than it should
...ail. However, no error is reported, and the -i output shows that the operation was completed as instructed -- which, of course, it could not have. The reason here is that, as far as I can see, in set_file_attrs, ATTRS_SET_NANO is not given and no attempt to set the mtime is made. Later however, in touch_up_dirs, set_modtime is called on the directory. It fails, but there is no error handling, because usually, the mtime would already have been set before, and an error would have become apparent already. (I guess that is anyway a dangerous assumption to make.) ================ All three cases have in com...
2008 Dec 04
4
DO NOT REPLY [Bug 5939] New: rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)
https://bugzilla.samba.org/show_bug.cgi?id=5939 Summary: rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1) Product: rsync Version: 3.0.4 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:
2009 May 15
1
rsync creates file twice
...ived 1 names [generator] flist start=5, used=1, low=0, high=0 [generator] i=5 3 usr/include/fltk-1.1/ mode=040755 len=4096 uid=0 gid=0 flags=5 recv_file_list done recv_generator(usr/include,4) set modtime of usr/include to (1242353855) Fri May 15 02:17:35 2009 recv_generator(usr/include/fltk-1.1,5) touch_up_dirs: usr (0) set modtime of usr to (1242354864) Fri May 15 02:34:24 2009 [generator] receiving flist for dir 2 recv_file_name(/usr/include/fltk-1.1/FL) recv_file_name(/usr/include/fltk-1.1/Fl) received 2 names [generator] flist start=7, used=2, low=0, high=1 [generator] i=7 4 usr/include/fltk-1.1/Fl m...