Fwd: Re: rsync + ssh -o -p -g -l
John Van Essen
vanes002 at umn.edu
Sat Mar 5 09:38:31 GMT 2005
(Email attachment quoted for the benefit of the mail archive...)
On Thu, 3 Mar 2005, michael mendoza <mike114x at yahoo.com> wrote:
> Hi, thank again.
> I used rsync today to copy 400 MB from a pc to other
> pc with rsync -avz -e ssh SourceDir
> root at ipDest:/dirDest/
> but in the source pc i write in the directory which i
> want copy: du -sh and i have 400 Mb but when i use
> rsync to copy to the other pc, and there i write du
> -sh i see than have 450 MB , is it normal?
> Example: pc A(source)
> #cd /home/mike/
> # du -sh
> # 400 MB
> pc B(destination)
> #cd /home/mike/ (or any dir destination)
> #du -sh
> # 450 Mb
> Why? what that mean?
1) There was something already in the destination tree. Since you are
not using --delete, there could be more files in the destination.
2) There are hard links in the source tree. Since you are not using
-H, they are now separate files at the destination. But this
scenario is unlikely - hardlinks aren't used by the typical user.
3) The atomic unit of storage is larger at the destination (e.g. 4096)
that at the source (e.g. 2048). So unused space would be greater.
But a 50 MB difference would require tens of thousands of files.
You should get directory tree listings (ls -lR) and compare them to
see what's going on.
> How can see with rsync more details of the transfers ,
> y try to use rsync -avvz but is the = rsync -avz, i
> want see more details, how can i do?
They shouldn't be the same...
Using more v's is the right thing to do. If two v's doesn't give
enough detail, try three v's.
John Van Essen Univ of Minn. Alumnus <vanes002 at umn.edu>
More information about the rsync