Re: --o-direct option

2008-02-27 Thread Jamie Lokier
Jerome Haltom wrote: > The problem is that during the rsync process the user's machine is > barely usable. The reason is because rsync reads these 2GB files... many > GBs of them. This causes the user's machine to repeatidly trash the page > cache. This really is Linux's fault. It should realize th

Re: running two rsync processes, synchronizing the same directories

2008-02-27 Thread Matt McCutchen
On Wed, 2008-02-27 at 22:29 +0100, cm wrote: > What happens if two rsync process are running, synchronizing the same > directories. In my case it means if two user are launching the rsync command > at the same time to equalize the same files / directories. Nothing terrible, but the two processes m

Re: Fragmentation on XFS

2008-02-27 Thread Wayne Davison
On Wed, Feb 27, 2008 at 02:07:06PM -0700, Rob Bosch wrote: > If there is 100% match shouldn't it just leave the file as is even if > the -I option is selected? The -I option tells rsync to transfer all the files (ignoring any quick-check time/size matches), so it is expected that it will update th

running two rsync processes, synchronizing the same directories

2008-02-27 Thread cm
Hi, first I got to say, thank you to the people who invested certainly much time to build this tool !! Nevertheless I need some information, which I couldn't find in the documentation. At the moment I have to build a web based synchronisation backend. In this case a user can initiate a rsync p

RE: Fragmentation on XFS

2008-02-27 Thread Rob Bosch
Wayne, thanks for your help on this issue. It turned out to be a user error (me) since the client was the pre5 client instead of the pre10. I reran the test with the pre10 client as you suggested and here are the results. The only odd thing I noticed is that even though all the data matched, the

DO NOT REPLY [Bug 5287] New: FreeBSD pre10 compilation warnings report

2008-02-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=5287 Summary: FreeBSD pre10 compilation warnings report Product: rsync Version: 3.0.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: minor Priority: P3 Co

Re: large number of small files to move

2008-02-27 Thread Matt McCutchen
On Mon, 2008-02-25 at 14:11 -0600, Terry wrote: > I have a large migration of a single system going from windows to > linux. We are moving 9 TB and 60 million files. I am planning on > using rsync to move this data. Are there any special considerations I > should have in mind when moving this mu

Re: Fragmentation on XFS

2008-02-27 Thread Rob Bosch
Let me know of any additional info or tests you need me to run. I'll halp any way I can. thanks. rob -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Fragmentation on XFS

2008-02-27 Thread Wayne Davison
On Mon, Feb 25, 2008 at 09:28:18PM -0700, Rob Bosch wrote: > I reran this test with the --no-whole-file option and received the exact > same results. Any idea on why some much data is being sent when the files > are exactly the same on both sides? Yeah, I hadn't noticed that your transfer had alr

Re: rsync-3.0.0pre10 and iconv

2008-02-27 Thread Wayne Davison
On Tue, Feb 26, 2008 at 02:14:34PM +0200, [EMAIL PROTECTED] wrote: > Has anyone got iso8859-1 to utf-8 conversion working with rsync-3.0.0pre10? It was failing when communicating with a daemon due to a missing setup_iconv() call. The attached patch fixes this. Thanks for your report! ..wayne..

RE: rsync-3.0.0pre10 and iconv

2008-02-27 Thread Tony Abernethy
Thankee! Thankee! Thankee! I am definitely switching to 3.0 or the next pre. (currently anything like that that actually gets to the other side is "gravy") (not all that bad since anything that actually matters is supposed to be in english not chinese ;-) This is on/to/through computers

RE: rsync-3.0.0pre10 and iconv

2008-02-27 Thread sami . pitko
> I think that UTF8 is simply used as the transport encoding. > The sending side will ensure that the filenames "on the wire" > are UTF8, and the receiving side will convert that UTF8 into > whatever is required. I checked with tcpdump what is being transmitted between the hosts and found that fi

Re: rsync-3.0.0pre10 and iconv

2008-02-27 Thread Paul Slootman
On Wed 27 Feb 2008, [EMAIL PROTECTED] wrote: > > So if I'm interpreting that right, UTF8 is hardcoded to always be one of > the conversion charsets. If rsync is sending, the conversion is always > to UTF8. If rsync is receiving, the conversion is always from UTF8. I think that UTF8 is simply used

RE: rsync-3.0.0pre10 and iconv

2008-02-27 Thread sami . pitko
Hello, > Has anyone got iso8859-1 to utf-8 conversion working with rsync-3.0.0pre10? I am answering to my own question. I looked at the setup_iconv function in rsync.c and found following code snippets: ... if ((ic_send = iconv_open(UTF8_CHARSET, charset)) == (iconv_t)-1) { ... ...