On 2013-12-10 00:11 (GMT-0800) L.A. Walsh composed: [Why she sent to factory list I have no idea. I missed noticing her switch from the en list.]
Felix Miata wrote:
source & target have same filesystem size, block size, filesystem type OS 11.4 running on both
Couple of scenarios to rule out:
1) going from
disk1 a -> 500G file b->empty
to
disk2 a=>empty b->500G file
---- --delete = --delete-during which means it won't try to delete a later encountered directory until it gets to copying 'b'. If your disk is 750G, your copy will die in the middle of copying "a".
Maybe delete-before would be better, though theoretically less safe, in that you might be deleting 500G before the copy on disk1 has safely made it to disk2. But if you are tight on disk space....
Given the result observed on running it a 2nd time, I believe the above describes close enough what happened, and I should have used delete-before.
2) If your target disk is more fragmented, then it will need more free-space extents(clusters) -- rather than 1 range with 2G, it might need 20 ranges with 100MB each.
That means disk 2 will need more "indirect" space to hold the extra ranges.
Likely this is happening too, but not the primary problem here. Carlos: not btrfs. MC would explain differences, but not necessarily the rsync behavior absent understanding what Linda explained. Michael: no idea why you brought up sparse. The filesystem's sparse files are mostly small. The largest mass of files by number and size are compressed. AFAICT, sparse is about transfer speed, not ultimate space consumption. Andrey: probably only one 1k hard linked file on that filesystem. Nearly nil soft links too. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org