-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Are you rsyncing from one to the other? Both of them to somewhere
else? One at a time to somewhere else? Why won't you just show your
actual command line and an ls -li of the correct source and incorrect
target?
On 01/23/2016 06:25 PM, dbonde+forum
On 2016-01-23 23:24, Kevin Korb wrote:
I need to know what the paths were so I know how they relate to the
file names you listed.
I posted the relevant parts of the path in a previous message
/Volumes/A/Backups.backupdb/mm/2011-06-23-040258/path/DSCF0748.JPG
/Volumes/B/Backups.backupdb/mm/2011
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I need to know what the paths were so I know how they relate to the
file names you listed.
On 01/23/2016 05:10 PM, dbonde+forum+rsync.lists.samba@gmail.com
wrote:
> On 2016-01-23 22:59, Kevin Korb wrote:
>> I want to know what your whole command l
On 2016-01-23 22:59, Kevin Korb wrote:
> I want to know what your whole command line was so I can understand
> your results.
% rsync -HzvhErlptgoDW --stats --progress --out-format="%t %f %b"
/source/ /destination/
(and after the interruption I removed z)
--
Please use reply-all for most replies
On 2016-01-23 22:02, Kevin Korb wrote:
What was your rsync source and target that made those?
What do you mean? Filesystem is HFS (Mac OS X). Rsync version is 3.1.2
from MacPorts. Source is a regular directory/folder on an external HD,
destination is a disk image.
--
Please use reply-all fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I want to know what your whole command line was so I can understand
your results.
On 01/23/2016 04:57 PM, dbonde+forum+rsync.lists.samba@gmail.com
wrote:
> On 2016-01-23 22:02, Kevin Korb wrote:
>> What was your rsync source and target that made t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What was your rsync source and target that made those?
On 01/23/2016 03:44 PM, dbonde+forum+rsync.lists.samba@gmail.com
wrote:
> On 2016-01-23 21:16, Kevin Korb wrote:
>> As long as it still sees both links it is fine.
>>
>> Essentially, the way
On 2016-01-23 21:16, Kevin Korb wrote:
> As long as it still sees both links it is fine.
>
> Essentially, the way it works is that whenever rsync -H (on the
> source) sees a file with a link count >1 it remembers the
> inode#>filename pair. If it finds another instance of that inode it
> then lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As long as it still sees both links it is fine.
Essentially, the way it works is that whenever rsync -H (on the
source) sees a file with a link count >1 it remembers the
inode#>filename pair. If it finds another instance of that inode it
then links t
On 2016-01-23 17:50, Kevin Korb wrote:
It will, assuming it sees both links in the same rsync run.
How does one handle interrupted transfers if one wants to preserve hard
links? Would --partial and --append-verify work?
--
Please use reply-all for most replies to avoid omitting the mailing l
On 2016-01-21 09:20, dbonde+forum+rsync.lists.samba@gmail.com wrote:
I run a rsync job transferring about 45 million files/approximately 1.8
TB data (a Mac OS X Time Machine backup) over a 100 MBit connection.
I use rsync 3.1.1 from MacPorts (I first tried the built in rsync,
version 2.6.9,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It will, assuming it sees both links in the same rsync run.
On 01/23/2016 11:46 AM, dbonde+forum+rsync.lists.samba@gmail.com
wrote:
> On 2016-01-21 09:20, dbonde+forum+rsync.lists.samba@gmail.com
> wrote:
>> I run a rsync job transferring abou
12 matches
Mail list logo
