similar to: getting a list of conflicting files

Hi, I tried to backup my gentoobox using rsync into a NTFS External Drive Rsync Failed And now there is no space lesft on my root directory "/" and kcore file size is 128 TiB and my External NTFS HDD makes scary sounds (Like it is working hardly) even when its not mounted rsync created some files/directories that i cant remove them on my External HDD using "rm -rf" , Please

I have the following script that I am working on #!/bin/bash date=$(date +%F--%T) #ssh parameters user=aquj001 remotehost=qa4app localdir=/home/aquj001/INFENG/scripts remotedir=/home/aquj001/recievingDir.$date linkdest=$(ssh $user@$remotehost /usr/linux/bin/readlink/ /home/aquj001/recievingDir.current) rsync -a --compress --link-dest=$linkdest --out-format='%i %n%L %l %M'

I can still read&write on the external hdd and on my laptop (which I have my gentoo there) I can't do anything on / because its filled up with /proc/kcore after "rsync failed" rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} /*

If your hard disk is making scary noises that could be the drive starting to fail have you tried to determine if the drive is still good or on the way out? On Thu, Apr 30, 2015 at 2:12 AM, Kezhawe <kezhawe28 at gmail.com> wrote: > Hi, > > I tried to backup my gentoobox using rsync into a NTFS External Drive > Rsync Failed And now there is no space lesft on my root directory

Greetings - I am trying to document the "value" section of a function. The function returns a list, but the list itself also has attributes. I would like to itemize the list entries, and itemize the attributes, but in between I would like to have a sentence or two about the attributes in general. However, for some reason this intermediate sentence won't show up in the compiled

What I want is a client-side log file itemized list of *all* the changes that rsync did on the remote machine. Using "--log-file" doesn't show everything. In particular, --log-file says nothing if the remote directory was populated using hard links from a --link-dest source. Any number of remote links and directories can be created, with no mention of any of it in the log file.

I've just released rsync 3.0.0pre10. I incorporated the latest daemon security fixes, and decided to include a few more minor bug fixes as well. If all goes well, this should be released as 3.0.0 final sometime next week. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the

I've just released rsync 3.0.0pre10. I incorporated the latest daemon security fixes, and decided to include a few more minor bug fixes as well. If all goes well, this should be released as 3.0.0 final sometime next week. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the

Hello! We are located in the UK, and we are planning to replace our old pbx with an asterisk based pbx. For outgoing calls our present pbx is connected to three PSTN lines which all have the same number. Internally, the pbx caters for quite a few extensions, and each extension can make outbound phone calls. Our telecom provider (your communications) gives us monthly itemized bills that list

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My guess is that it is the atimes patch causing the problem. Normally rsync would never say "u" in the itemized output as it is "reserved for future use". Plus copying the file would change the atime. On 03/28/2016 08:44 AM, Albert Berger wrote: > On Mon, Mar 28, 2016 at 08:11:07AM -0400, Kevin Korb wrote: >> -----BEGIN

I've released rsync 2.6.4pre3. I'm hoping that this will be pretty close to the final version for 2.6.4, so please beat on this and let me know if anything weird turns up! IMPORTANT: protocol 29 was revised in pre3 to be incompatible with pre1 and pre2, so be sure to update all your pre-release versions at the same time. Rsync has code in it to detect that it is talking to an older

I've released rsync 2.6.4pre3. I'm hoping that this will be pretty close to the final version for 2.6.4, so please beat on this and let me know if anything weird turns up! IMPORTANT: protocol 29 was revised in pre3 to be incompatible with pre1 and pre2, so be sure to update all your pre-release versions at the same time. Rsync has code in it to detect that it is talking to an older

You are using rsync -a which copies (preserves) the timestamp. Meaning that rsync will copy the file then back-date it to the timestamp of the source file. Most copying tools do not do this though cp's -a does it too. Note that your itemized output says that the timestamp is different meaning that the file has changed since rsync last ran. Without the -a (or the included -t) the

https://bugzilla.samba.org/show_bug.cgi?id=11496 Bug ID: 11496 Summary: itemized logging of transferred bytes is cumulative instead of per file Product: rsync Version: 3.1.0 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=2781 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-06-09 09:34 ------- Rsync doesn't output "uptodate" for

Hi Kevin, The -a flag in this instance is not back-dating the timestamp of the copied file to the source file. It is modifying it to the time of transfer and leaving it that way. Then any time I rerun that command it always updates the timestamp since it is always making it the time of transfer. I have a source file the has a modification date of 2015 and when I rsync it to day with -a the copied

That isn't how rsync should work with -a. Is something preventing it from backdating the file? What is the filesystem? Can you try copying your 2015 file with cp -a? On 10/9/24 14:56, McDowell, Blake wrote: > Hi Kevin, > > The -a flag in this instance is not back-dating the timestamp of the > copied file to the source file. It is modifying it to the time of > transfer

On Mon, Mar 28, 2016 at 08:11:07AM -0400, Kevin Korb wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about these files? > > Also, what is --atimes? Is this the Apple modified rsync for OSX? > > On 03/28/2016 07:51 AM, Albert Berger wrote: > > Greetings, > > > > when the daily system backup with rsync is

I have been using backuppc (rsync protocol) to backup up a Linux web server onto a local server for a number of years. I recall that data volumes were quite low (about 40MB), regardless of whether I was doing full or incremental backups. I recently switched to both a new web server and backuppc server. Early morning traffic volumes when backuppc runs are much higher than expected - I have

https://bugzilla.samba.org/show_bug.cgi?id=4412 Summary: --dry-run output inaccurate due to implied symlink Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: