Matthias Schniedermeyer wrote:
- I don't see what your problem is
It doesn't work as they thought it would?
That said -- the man page says under "-u":
-u, --update skip files that are newer on the
receiver
Technically, directories are not
samba-b...@samba.org wrote:
https://bugzilla.samba.org/show_bug.cgi?id=10322
--- Comment #1 from roland devz...@web.de 2013-12-14 13:24:46 UTC ---
rsync 3.0.8 runs with 45 mb/sec
45mb/s with cygwin?
are you really sure?
afaik, rsync via cygwin always is dead slow, especially in
On 12/7/2013 11:10 AM, Leen Besselink wrote:
If you want to check the data, you need -c I believe.
Which will be REAL slow.
If you want to compare the files use 'diff' -qr /src /dest'
It will still read the files like rsync would, BUT it won't compute
a checksum which is usually a slow
On 12/3/2013 6:01 AM, Holger Hoffstaette wrote:
On Mon, 02 Dec 2013 00:30:58 -0800, Linda A. Walsh wrote:
Was there some reason that patch got dropped?
AFAIK it was never applied in the first place.
It was in opensuse up to and including their latest release opensuse 13.1.
I
On 12/2/2013 11:31 AM, Charles Marcus wrote:
Hello,
I'm going to be moving a filesystem around, and was planning on using
rsync to do it, so like to get some advice from those more experienced
than I (both using rsync, and moving filesystems)...
---
If you have 'star' on your system, it
On 12/4/2013 4:01 AM, Charles Marcus wrote:
Thanks Linda... I was initially planning on using cp for this, but
someone on the gentoo list convinced me that rsync was better (not
sure why now)...
cp didn't support ACL's and xattrs about 3-4 years ago. rsync was
maybe the 2nd
large
In thinking about this some more, you probably
want to limit your O_DIRECT to just opens on files --
not sockets.
I think that might be the cause of the error I got.
The other stuff may still apply, but may be OS dependent.
It doesn't look like it is real easy to tell in the
open routine
Sorry for the multiple posts, am thinking about this problem
in between working on other stuff... and stuff comes up.
But bottom line -- I would look at the source of coreutils dd program
and find out how they do direct I/O. I know they had to deal with
alignment issues when the Linux kernel
I wondered about that as well -- could speed things
up by 30% over going through the slow linux buffers.
One thing that the 'dd' people found out though was
that if you do direct I/O, memory and your I/O really
do have to line up -- it may be that only 512 byte alignment
is necessary (or 4096 on
Dag Wieers wrote:
On Thu, 14 Feb 2013, Brian K. White wrote:
On 2/14/2013 9:50 AM, Dag Wieers wrote:
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the
Dag Wieers wrote:
Hi,
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the patches here.
Sigh.
It hasn't been done because it isn't
Ben Oswald wrote:
Hey,
I'm using rsync to backup my server but there is a problem because
rsync is using very huge amounts traffic. But first to the setup. The
server I backup has 4GB of data and I use the following command to
backup this data. /usr/bin/rsync -aze 'ssh -i
Karl O. Pinc wrote:
If you want help with your problem you're going to have
to describe exactly what you're doing; what command
you're running, what version of rsync, and so forth.
---
Thanks...was going to file a bug report on it when I got
time... just haven't gotten to it.
Already worked
The volume I am differencing a snapshot with has
595,400 dirs (424994 w/link count=2)
5,703,820 files.
The diff volume starts with
233,764 files (a large multi-day diff)
but 289,215 dirs!
I ran a script to clean out all the empty dirs...final tally:
same # of files: 233764, but
#dirs:
I'm using: (according to ps)
/usr/bin/rsync --archive --human-readable --acls --xattrs --hard-links
--no-inc-recursive --prune-empty-dirs --whole-file --one-file-system
--compare-dest=/home/. --exclude=**/.recycle/**
--exclude=CPAN-ishtar-build-cache/**
Benjamin Ward wrote:
but it seems to not behave the way i thought it would.
How did you think it would work?
I use it and will describe what it does w/my example:
I'm using: (according to ps)
/usr/bin/rsync --archive --human-readable --acls --xattrs --hard-links
--no-inc-recursive
In looking at source, I started at fileio and found
write routines but no read routines.
I found a 'WRITE_SIZE' (32K), but no 'READ_SIZE' --
is that' what the MAX_MAP_SIZE (256K)?
I would like to make so that rsync can use larger I/O sizes if
(maybe a command line option?)
The map routine
Justin T Pryzby wrote:
Note that --whole-file is the default when both the source and
destination are specified as local paths, and implies that the file
is copied without the delta transfer algorithm.
---
I am using the 'whole-file' copy, 'explicitly', as I didn't know
that was the default in
How can I show it to you? I'm pretty sure I can produce it on demand -- just
take another snapshot and do a rsync w/o the no-i-r switch...
But it's not like I can send you a HD via email...they are sorta big...?
Wayne Davison wrote:
On Sun, Aug 5, 2012 at 1:50 AM, Linda Walsh rs
Paul Slootman wrote:
On Thu 09 Aug 2012, Linda Walsh wrote:
Anyway, thanks for the history update. I have a feeling rsync is afraid to use
memory -- and really, it should try to use alot of memory to optimize transfers,
I have had rsync fail after using up 8GB memory + 4GB swap, so I'm
Dan Stromberg wrote:
I may be mistaken, but I heard at one time that rsync was noticeably
slower when asked to preserve hard links. I'm guessing this is a matter
of CPU requirements rather than I/O requirements, but that's just a guess.
---
I didn't realize at the time I wrote it,
usage.
My storage requirements would seriously go up with hard links ignored.
(especially since I run deduplication on my files now and then that
links duplicates together!)
Linda Walsh wrote:
Familiar? protocol error on a local file copy?
How can I have a proto incompat when
Familiar? protocol error on a local file copy?
How can I have a proto incompat when it it is talking to itself?...
This was on the ERROUT...
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
Broken pipe (32)
File-list index 531530 not in 531937 - 533437
Jack Walter wrote:
Hi,
I'm using cwrsync with rsync 3.0.8 atm and after syncing a file to Strato
HiDrive and back to the local machine the new permissions contain
this entry:
None (UK-DT-01\None)
with Read, Execute; Read and Write (allowed) permissions.
It takes a few seconds before this
But in copying real files, there's alot more going on that file I/O...
and that's where rysnc spends most of its time.
If file-I/O dominates, and not much data to xfer, rsync is a win, but if
data to
xfer is 'full' .. rsync will always be notably slower.
(as you note below...though it's worse
dhtmldude wrote:
I'm using Rsync 3.1.0 and VanDyke VShell for SSH.
Is there a reason why you are using the VD VS when you likely have
cygwin's 'ssh' built in as well? Cygwin's ssh was ~20-30% faster than
VD's technology (I benched it against their VSH/VCP tools in their
SecCRT
dhtmldude wrote:
Hello, either cygwin or rsync (version 3.0.6) is prepending /cygwin/c/ to the
source path from the command line.
C:\CMS\PageGeneratorrsync -avc --delete -vvv --protocol=20 -e ssh.exe -i
C:\cms\PageGenerator\qa_rsa
\\cagecfsu1.saifg.rbc.com\YCM0\InternalCache\test_aug17/
Hey Rob, some clarifications/comments...:-)
I was talking about the undesirable fragmentation that results from using
rsync as a type of smart-copy -- copying files from a source to a
destination with the target rsync invoked by the source-tree process (i.e.
rsync isn't a daemon). For me, that's
I'm very sorry for being late to the party on this note, but I'm
not sure what the original trigger for this fragmentation problem
was... I thought (imagining?) that one issue was related to
performance under cygwin.
I see the solution is going towards a pre-allocation switch, but
the question I
29 matches
Mail list logo
